diff options
| author | Viresh Kumar <viresh.kumar@linaro.org> | 2024-06-18 12:42:29 +0300 |
|---|---|---|
| committer | Juergen Gross <jgross@suse.com> | 2024-07-02 13:23:42 +0300 |
| commit | 611ff1b1ae989a7bcce3e2a8e132ee30e968c557 (patch) | |
| tree | 684af3e201002c451f9ddabfa63fbffd53f1bd0d /arch/arm | |
| parent | 1c682593096a487fd9aebc079a307ff7a6d054a3 (diff) | |
| download | linux-611ff1b1ae989a7bcce3e2a8e132ee30e968c557.tar.xz | |
xen: privcmd: Fix possible access to a freed kirqfd instance
Nothing prevents simultaneous ioctl calls to privcmd_irqfd_assign() and
privcmd_irqfd_deassign(). If that happens, it is possible that a kirqfd
created and added to the irqfds_list by privcmd_irqfd_assign() may get
removed by another thread executing privcmd_irqfd_deassign(), while the
former is still using it after dropping the locks.
This can lead to a situation where an already freed kirqfd instance may
be accessed and cause kernel oops.
Use SRCU locking to prevent the same, as is done for the KVM
implementation for irqfds.
Reported-by: Al Viro <viro@zeniv.linux.org.uk>
Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Reviewed-by: Juergen Gross <jgross@suse.com>
Link: https://lore.kernel.org/r/9e884af1f1f842eacbb7afc5672c8feb4dea7f3f.1718703669.git.viresh.kumar@linaro.org
Signed-off-by: Juergen Gross <jgross@suse.com>
Diffstat (limited to 'arch/arm')
0 files changed, 0 insertions, 0 deletions