CVE-2024-41080: io_uring: fix possible deadlock in io_register_iowq_max_workers()
First published: Mon Jul 29 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | <6.9.11 | |
| debian/linux | <=5.10.223-1 | 5.10.234-1 6.1.129-1 6.1.128-1 6.12.20-1 6.12.21-1 |
| debian/linux-6.1 | 6.1.129-1~deb11u1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/73254a297c2dd094abec7c9efee32455ae875bdf
- https://git.kernel.org/stable/c/b571a367502c7ef94c688ef9c7f7d69a2ce3bcca
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41080
- https://nvd.nist.gov/vuln/detail/CVE-2024-41080
- https://launchpad.net/bugs/cve/CVE-2024-41080
- https://security-tracker.debian.org/tracker/CVE-2024-41080
- https://ubuntu.com/security/CVE-2024-41080
- https://git.kernel.org/linus/73254a297c2dd094abec7c9efee32455ae875bdf
- https://git.kernel.org/stable/c/b17397a0a5c56e111f61cb5b77d162664dc00de9
- https://git.kernel.org/stable/c/97ed7ff58de66c544692b3c2b988f3f594348de0
- https://git.kernel.org/stable/c/fdacd09f2ddf7a00787291f08ee48c0421e5b709
- https://git.kernel.org/stable/c/950ac86cff338ab56e2eaf611f4936ee34893b63
Frequently Asked Questions
What is the severity of CVE-2024-41080?
The severity of CVE-2024-41080 is categorized as a moderate impact due to the potential for a deadlock in the Linux kernel.
How do I fix CVE-2024-41080?
To fix CVE-2024-41080, it is recommended to update to the latest patched versions of the Linux kernel provided by your distribution.
Which versions of the Linux kernel are affected by CVE-2024-41080?
CVE-2024-41080 affects Linux kernel versions prior to 5.10.226 and certain patched versions within the 6.1 series.
Is CVE-2024-41080 a remote exploit vulnerability?
CVE-2024-41080 is not considered a remote exploit vulnerability, as it primarily involves local conditions leading to a deadlock.
What is io_register_iowq_max_workers() in relation to CVE-2024-41080?
The function io_register_iowq_max_workers() is involved in the deadlock issue identified in CVE-2024-41080 within the Linux kernel's io_uring subsystem.
- agent/title
- agent/first-publish-date
- agent/type
- agent/weakness
- agent/remedy
- agent/severity
- agent/author
- agent/references
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/trending
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-cve
- collector/usn-cve
- source/Ubuntu
- collector/launchpad-cve
- source/Launchpad
- collector/security-tracker-debian
- source/Debian
- agent/source
- agent/softwarecombine
- agent/tags
- agent/description
- agent/event
- vendor/linux
- canonical/linux kernel
- package-manager/debian