First published: Wed Sep 04 2024(Updated: )
In 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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | <6.6.46 | |
Linux Kernel | >=6.7<6.10.5 | |
debian/linux | <=5.10.223-1<=5.10.226-1<=6.1.123-1<=6.1.119-1 | 6.12.11-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2024-44957 has not been specifically rated, but it affects the Linux kernel's handling of IRQ file descriptors.
To fix CVE-2024-44957, update to the Linux kernel version 6.12.11-1 or later.
CVE-2024-44957 affects Linux kernel versions prior to 6.7 and versions from 6.10.5 and below.
The impact of CVE-2024-44957 is related to potential race conditions in IRQ handling, which could lead to unexpected behavior.
There are no specific workarounds mentioned for CVE-2024-44957, so updating the kernel is recommended.