All reports
Medium

kernel: xen: privcmd: Fix possible access to a freed kirqfd instance

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2024-46762

Probability of exploitation in the next 30 days: 0.25%

FIRST EPSS · 2026-11-21

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.

A flaw was found in the Linux kernel's xen: privcmd component. This use-after-free vulnerability occurs due to a race condition between simultaneous ioctl calls to privcmd_irqfd_assign() and privcmd_irqfd_deassign(). A local attacker could exploit this by causing a kirqfd instance to be freed while still in use, which leads to a kernel oops and a denial of service.