CVE-2024-46829

rtmutex: Drop rt_mutex::wait_lock before scheduling

MEDIUM

5.5

CVSS Score

Published: September 27, 2024 at 12:39 PM UTC

Updated: June 17, 2026 at 07:56 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 3.10.49v ≥ 3.12.25v ≥ 3.14.10v ≥ 3.15.3v ≥ 3.2.61v ≥ 3.4.993.10.49 ≤ v < 3.113.12.25 ≤ v < 3.133.14.10 ≤ v < 3.153.15.3 ≤ v < 3.163.16 ≤ v < 4.19.3223.16 ≤ v < 5.10.2263.16 ≤ v < 5.15.1673.16 ≤ v < 5.4.2843.16 ≤ v < 6.1.1103.16 ≤ v < 6.10.103.16 ≤ v < 6.113.16 ≤ v < 6.6.513.2.61 ≤ v < 3.33.4.99 ≤ v < 3.54.20 ≤ v < 5.4.2845.11 ≤ v < 5.15.1675.16 ≤ v < 6.1.1105.5 ≤ v < 5.10.2266.2 ≤ v < 6.6.516.7 ≤ v < 6.10.101201613a70dd34bd347ba2970919b3f1d5fbfb4a2b1f3807ed9cafb59c956ce76a05d25e67103f2e3.10.49 3.12.25 3.14.10 3.15.3 3.2.61 3.4.993d5c9340d1949733eb37616abd15db36aef9a57c6.11 rc1 6.11 rc2 6.11 rc3 6.11 rc4 6.11 rc5 6.11 rc695f9aded9436aa3ce714aeff3f45fcc1431df7d2a2e64fcdc83c645813f7b93e4df291841ba7c625ea018da95368adfb700689bd9842714f7c3db665fb52f40e085ef4074f1335672cd62c1f832af13b

Vendor states this is fixed in 1401da1486dc1cdbef6025fd74a3977df3a3e5d0 (fixed)

Vendor states this is fixed in 432efdbe7da5ecfcbc0c2180cfdbab1441752a38 (fixed)

Vendor states this is fixed in 6a976e9a47e8e5b326de671811561cab12e6fb1f (fixed)

Vendor states this is fixed in 85f03ca98e07cd0786738b56ae73740bce0ac27f (fixed)

Vendor states this is fixed in 93f44655472d9cd418293d328f9d141ca234ad83 (fixed)

Vendor states this is fixed in a92d81c9efec9280681c27a2c0a963fd0f1338e0 (fixed)

Vendor states this is fixed in d33d26036a0274b472299d7dcdaa5fb34329f91b (fixed)

Vendor states this is fixed in f13b5afc5c4889569d84c3011ce449f61fccfb28 (fixed)

Affected range stops below 3.11, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.13, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.15, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 3.16 (unaffected)

Affected range stops below 3.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.5, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 4.19.322 (unaffected)

Vendor states this is fixed in 5.10.226 (unaffected)

Vendor states this is fixed in 5.15.167 (unaffected)

Vendor states this is fixed in 5.4.284 (unaffected)

Vendor states this is fixed in 6.1.110 (unaffected)

Vendor states this is fixed in 6.10.10 (unaffected)

Vendor states this is fixed in 6.11 (unaffected)

Vendor states this is fixed in 6.6.51 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references