CVE-2024-39292: um: Add winch to winch_handlers before registering winch IRQ
In the Linux kernel, the following vulnerability has been resolved:
um: Add winch to winchhandlers before registering winch IRQ
Registering a winch IRQ is racy, an interrupt may occur before the winch is added to the winchhandlers list.
If that happens, registerwinchirq() adds to that list a winch that is scheduled to be (or has already been) freed, causing a panic later in winchcleanup().
Avoid the race by adding the winch to the winchhandlers list before registering the IRQ, and rolling back if umrequestirq() fails.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.27-1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-39292?
CVE-2024-39292 has been classified with a moderate severity level due to the potential for race conditions in the Linux kernel.
How can I fix CVE-2024-39292?
To fix CVE-2024-39292, upgrade to the recommended patched versions, such as 5.10.223-1, 5.10.226-1, 6.1.123-1, or higher.
Which versions of the Linux kernel are affected by CVE-2024-39292?
CVE-2024-39292 affects various versions of the Linux kernel, ranging from 2.6.23 up to 6.10.0-rc1.
What is a winch IRQ in relation to CVE-2024-39292?
In CVE-2024-39292, the winch IRQ refers to an interrupt request in the Linux kernel that can be registered in a race-prone manner.
Is CVE-2024-39292 specific to any Linux distributions?
CVE-2024-39292 is relevant to all distributions using the affected versions of the Linux kernel, including those derived from Debian.