Description
In the Linux kernel, the following vulnerability has been resolved: 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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
f8941e6c4c712948663ec5d7bbb546f1a0f4e3f6 to < e997b357b13a7d95de31681fc54fcc34235fa527affectedf8941e6c4c712948663ec5d7bbb546f1a0f4e3f6 to < 112fd2f02b308564724b8e81006c254d20945c4baffectedf8941e6c4c712948663ec5d7bbb546f1a0f4e3f6 to < 611ff1b1ae989a7bcce3e2a8e132ee30e968c557affected
Linux Linux
Default version status: affected
6.6affected0 to < 6.6unaffected6.6.51 to ≤ 6.6.*unaffected6.10.10 to ≤ 6.10.*unaffected6.11 to ≤ *unaffected