CVE-2024-46829: rtmutex: Drop rt_mutex::wait_lock before scheduling
In the Linux kernel, the following vulnerability has been resolved:
rtmutex: Drop rtmutex::waitlock before scheduling
rtmutexhandledeadlock() is called with rtmutex::waitlock held. In the good case it returns with the lock held and in the deadlock case it emits a warning and goes into an endless scheduling loop with the lock held, which triggers the 'scheduling in atomic' warning.
Unlock rtmutex::waitlock in the dead lock case before issuing the warning and dropping into the schedule for ever loop.
[ tglx: Moved unlock before the WARN(), removed the pointless comment, massaged changelog, added Fixes tag ]
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-46829?
CVE-2024-46829 has a moderate severity rating due to potential deadlock situations in the Linux kernel's rtmutex implementation.
How do I fix CVE-2024-46829?
To fix CVE-2024-46829, update the Linux kernel to a version that includes the patch for this vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-46829?
CVE-2024-46829 affects Linux kernel versions from 3.2.61 to 6.11-rc6.
Is CVE-2024-46829 exploitable remotely?
CVE-2024-46829 is not classified as remotely exploitable as it primarily impacts local thread scheduling.
What systems should I prioritize for patching against CVE-2024-46829?
Focus on systems running affected Linux kernel versions, particularly those used in critical applications or services.