xen: privcmd: Switch from mutex to spinlock for irqfds
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.6.466.10.56.11In the Linux kernel, the following vulnerability has been resolved:
xen: privcmd: Switch from mutex to spinlock for irqfds
irqfd_wakeup() gets EPOLLHUP, when it is called by eventfd_release() by way of wake_up_poll(&ctx->wqh, EPOLLHUP), which gets called under spin_lock_irqsave(). We can't use a mutex here as it will lead to a deadlock.
Fix it by switching over to a spin lock.
From the CVE record · Linux
The Linux kernel’s Xen privcmd irqfd handling can deadlock because irqfd_wakeup() uses a mutex when eventfd_release() calls it while holding a spinlock. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with Xen privcmd irqfds should check their versions; affected versions are not specified.