CVE-2023-53461
Last modified
CVE-2023-53461 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: io_uring: wait interruptibly for request completions on exit WHen the ring exits, cleanup is done and the final cancelation and waiting on completions is done by io_ring_exit_work. That function is invoked by kworker, which doesn't take any signals. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: io_uring: wait interruptibly for request completions on exit WHen the ring exits, cleanup is done and the final cancelation and waiting on completions is done by io_ring_exit_work. That function is invoked by kworker, which doesn't take any signals. Because of that, it doesn't really matter if we wait for completions in TASK_INTERRUPTIBLE or TASK_UNINTERRUPTIBLE state. However, it does matter to the hung task detection checker! Normally we expect cancelations and completions to happen rather quickly. Some test cases, however, will exit the ring and park the owning task stopped (eg via SIGSTOP). If the owning task needs to run task_work to complete requests, then io_ring_exit_work won't make any progress until the task is runnable again. Hence io_ring_exit_work can trigger the hung task detection, which is particularly problematic if panic-on-hung-task is enabled. As the ring exit doesn't take signals to begin with, have it wait interruptibly rather than uninterruptibly. io_uring has a separate stuck-exit warning that triggers independently anyway, so we're not really missing anything by making this switch.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.1, < 5.10.188 |
| Linux | Linux Kernel | >= 5.11, < 5.15.121 |
| Linux | Linux Kernel | >= 5.16, < 6.1.39 |
| Linux | Linux Kernel | >= 6.2, < 6.4.4 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2023-53461?
How severe is CVE-2023-53461?
How do I fix CVE-2023-53461?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-53456In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53457In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53458In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53459In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-5346Type confusion in V8 in Google Chrome prior to 117.0.5938.14…8.8
- CVE-2023-53460In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53462In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53463In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53464In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53465In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2023-53466In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53467In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2023-53461?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
