Answer in brief
CVE-2023-53461 records a Medium severity (CVSS 5.5) vulnerability in io_uring: wait interruptibly for request completions on exit. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2b188cc1bb857a9d4701ae59aa7768b5124e262e <28e649dc9947e6525c95e32aa9a8e147925e3f56 || >=2b188cc1bb857a9d4701ae59aa7768b5124e262e <8e29835366138389bfad3b31ea06960d0a77bf77 || >=2b188cc1bb857a9d4701ae59aa7768b5124e262e <b50d6e06cca7b67a3d73ca660dda27662b76e6ea || >=2b188cc1bb857a9d4701ae59aa7768b5124e262e <58e80cb68b057e974768792c34708c6957810486 || >=2b188cc1bb857a9d4701ae59aa7768b5124e262e <4826c59453b3b4677d6bf72814e7ababdea86949 | 28e649dc9947e6525c95e32aa9a8e147925e3f56, 8e29835366138389bfad3b31ea06960d0a77bf77, b50d6e06cca7b67a3d73ca660dda27662b76e6ea, 58e80cb68b057e974768792c34708c6957810486, 4826c59453b3b4677d6bf72814e7ababdea86949 |
| Linux/Linuxgeneric | 5.1 | Not reported |
Published upstream
Oct 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.