CVE-2024-46829 rtmutex: Drop rt_mutex::wait_lock before scheduling

Medium 5.5 Published Updated

A locking bug in the Linux kernel's rtmutex deadlock handler causes an infinite scheduling loop, leading to system denial of service.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2024-46829?

CVE-2024-46829 is a medium-severity denial of service vulnerability in Linux kernel, published on 27 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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 ]

Weakness: CWE-667

Which versions are affected by CVE-2024-46829?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2024-46829?

Apply the vendor's patch.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2024-46829 being exploited?

There is no known exploitation of CVE-2024-46829 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as AZL-49813, BELL-CVE-2024-46829, DEBIAN-CVE-2024-46829, GHSA-6rh8-ww5v-vx2c, UBUNTU-CVE-2024-46829.

Is CVE-2024-46829 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free