Tracker / CVE-2024-46829
CVE-2024-46829
Medium 5.5
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 ]
Affected products and versions
| linux | linux_kernel |
|---|---|
| linux | linux_kernel · 3.10.49 → 3.11 |
| linux | linux_kernel · 3.12.25 → 3.13 |
| linux | linux_kernel · 3.14.10 → 3.15 |
| linux | linux_kernel · 3.15.3 → 3.16 |
| linux | linux_kernel · 3.16 → 4.19.322 |
| linux | linux_kernel · 3.2.61 → 3.3 |
| linux | linux_kernel · 3.4.99 → 3.5 |
| linux | linux_kernel · 4.20 → 5.4.284 |
| linux | linux_kernel · 5.11 → 5.15.167 |
| linux | linux_kernel · 5.16 → 6.1.110 |
| linux | linux_kernel · 5.5 → 5.10.226 |
| linux | linux_kernel · 6.2 → 6.6.51 |
| linux | linux_kernel · 6.7 → 6.10.10 |
Analysis
This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.