CVE-2024-41080 io_uring: fix possible deadlock in io_register_iowq_max_workers()

Medium 5.5 Published Updated

A local attacker can trigger a deadlock in the Linux kernel's io_uring subsystem, causing a 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-41080?

CVE-2024-41080 is a medium-severity vulnerability in Linux kernel, published on 29 Jul 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:

io_uring: fix possible deadlock in io_register_iowq_max_workers()

The io_register_iowq_max_workers() function calls io_put_sq_data(), which acquires the sqd->lock without releasing the uring_lock. Similar to the commit 009ad9f0c6ee ("io_uring: drop ctx->uring_lock before acquiring sqd->lock"), this can lead to a potential deadlock situation.

To resolve this issue, the uring_lock is released before calling io_put_sq_data(), and then it is re-acquired after the function call.

This change ensures that the locks are acquired in the correct order, preventing the possibility of a deadlock.

Weakness: CWE-667

Which versions are affected by CVE-2024-41080?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2024-41080?

Apply the vendor's patch.

Is CVE-2024-41080 being exploited?

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

All Linux kernel vulnerabilities

Sources

Also known as AZL-47985, AZL-48051, BELL-CVE-2024-41080, DEBIAN-CVE-2024-41080, GHSA-hxr9-q428-7jhg, UBUNTU-CVE-2024-41080.

Is CVE-2024-41080 in your software?

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

Check your SBOMs for free