CVE-2024-50060: io_uring: check if we need to reschedule during overflow flush
First published: Mon Oct 21 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: io_uring: check if we need to reschedule during overflow flush In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it'll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while. Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There's no state to maintain here as overflows always prune from head-of-list, hence it's fine to drop and reacquire the locks at the end of the loop.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux kernel | >=6.1<6.1.113 | |
| Linux kernel | >=6.6<6.6.57 | |
| Linux kernel | >=6.11<6.11.4 | |
| Linux Kernel | >=6.1<6.1.113 | |
| Linux Kernel | >=6.6<6.6.57 | |
| Linux Kernel | >=6.11<6.11.4 | |
| debian/linux | <=5.10.223-1<=5.10.234-1 | 6.1.129-1 6.1.128-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/a2493904e95ce94bbec819d8f7f03b99976eb25c
- https://git.kernel.org/stable/c/f4ce3b5d26ce149e77e6b8e8f2058aa80e5b034e
- https://git.kernel.org/stable/c/c2eadeafce2d385b3f6d26a7f31fee5aba2bbbb0
- https://git.kernel.org/stable/c/eac2ca2d682f94f46b1973bdf5e77d85d77b8e53
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50060
- https://nvd.nist.gov/vuln/detail/CVE-2024-50060
- https://launchpad.net/bugs/cve/CVE-2024-50060
- https://security-tracker.debian.org/tracker/CVE-2024-50060
- https://ubuntu.com/security/CVE-2024-50060
- https://git.kernel.org/linus/eac2ca2d682f94f46b1973bdf5e77d85d77b8e53
Frequently Asked Questions
What is the severity of CVE-2024-50060?
CVE-2024-50060 has been rated with a moderate severity level due to its potential impact on system stability.
How do I fix CVE-2024-50060?
To fix CVE-2024-50060, you should update the Linux kernel to a version newer than 6.1.113 or 6.6.57 or 6.11.4.
What systems are affected by CVE-2024-50060?
CVE-2024-50060 affects various versions of the Linux kernel, specifically those between 6.1.0 to 6.1.113, 6.6.0 to 6.6.57, and 6.11.0 to 6.11.4.
What type of vulnerability is CVE-2024-50060?
CVE-2024-50060 is classified as a reliability vulnerability related to the io_uring implementation in the Linux kernel.
Is there a workaround for CVE-2024-50060?
There are no specific workarounds recommended for CVE-2024-50060; updating the kernel is the preferred action.
- agent/title
- agent/first-publish-date
- agent/type
- agent/author
- agent/severity
- agent/remedy
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/launchpad-cve
- source/Launchpad
- agent/references
- agent/source
- agent/tags
- collector/usn-cve
- source/Ubuntu
- agent/description
- agent/event
- collector/security-tracker-debian
- source/Debian
- agent/softwarecombine
- collector/nvd-cve
- vendor/linux
- canonical/linux kernel
- version/linux kernel/6.1
- version/linux kernel/6.6
- version/linux kernel/6.11
- package-manager/debian