rtmutex: Drop rt_mutex::wait_lock before scheduling
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3d5c9340d1949733eb37616abd15db36aef9a57c · < 85f03ca98e07cd0786738b56ae73740bce0ac27f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
rtmutex: Drop rt_mutex::wait_lock before scheduling
rt_mutex_handle_deadlock() is called with rt_mutex::wait_lock 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 rt_mutex::wait_lock 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 ]
From the CVE record · Linux
In a deadlock case, the Linux kernel’s rtmutex code schedules while holding a lock, triggering a “scheduling in atomic” warning. The input does not describe an attacker action or specify whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their versions against the vendor advisory; affected versions are not specified in the input.