CVE-2023-53461
published 2025-10-01CVE-2023-53461: In the Linux kernel, the following vulnerability has been resolved: io_uring: wait interruptibly for request completions on exit WHen the ring exits, cleanup…
PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.14%
4.3th percentile
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.
Affected
15 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.52-1 (bookworm) | linux 6.1.52-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 2b188cc1bb857a9d4701ae59aa7768b5124e262e < 28e649dc9947e6525c95e32aa9a8e147925e3f56 | 28e649dc9947e6525c95e32aa9a8e147925e3f56 |
| linux | linux | >= 2b188cc1bb857a9d4701ae59aa7768b5124e262e < 8e29835366138389bfad3b31ea06960d0a77bf77 | 8e29835366138389bfad3b31ea06960d0a77bf77 |
| linux | linux | >= 2b188cc1bb857a9d4701ae59aa7768b5124e262e < b50d6e06cca7b67a3d73ca660dda27662b76e6ea | b50d6e06cca7b67a3d73ca660dda27662b76e6ea |
| linux | linux | >= 2b188cc1bb857a9d4701ae59aa7768b5124e262e < 58e80cb68b057e974768792c34708c6957810486 | 58e80cb68b057e974768792c34708c6957810486 |
| linux | linux | >= 2b188cc1bb857a9d4701ae59aa7768b5124e262e < 4826c59453b3b4677d6bf72814e7ababdea86949 | 4826c59453b3b4677d6bf72814e7ababdea86949 |
| linux | linux_kernel | >= 0 < 5.10.191-1 | 5.10.191-1 |
| linux | linux_kernel | >= 0 < 6.1.52-1 | 6.1.52-1 |
| linux | linux_kernel | >= 0 < 6.4.4-1 | 6.4.4-1 |
| linux | linux_kernel | >= 0 < 6.4.4-1 | 6.4.4-1 |
| linux | linux_kernel | >= 5.1 < 5.10.188 | 5.10.188 |
| linux | linux_kernel | >= 5.11 < 5.15.121 | 5.15.121 |
| linux | linux_kernel | >= 5.16 < 6.1.39 | 6.1.39 |
| linux | linux_kernel | >= 6.2 < 6.4.4 | 6.4.4 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-w27r-hww7-6vv2: In the Linux kernel, the following vulnerability has been resolved:
io_uring: wait interruptibly for request completions on exit
WHen the ring exits
ghsa_unreviewed·2025-10-01
CVE-2023-53461 [MEDIUM] GHSA-w27r-hww7-6vv2: In the Linux kernel, the following vulnerability has been resolved:
io_uring: wait interruptibly for request completions on exit
WHen the ring exits
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 i
OSV
CVE-2023-53461: In the Linux kernel, the following vulnerability has been resolved: io_uring: wait interruptibly for request completions on exit WHen the ring exits,
osv·2025-10-01·CVSS 5.5
CVE-2023-53461 [MEDIUM] CVE-2023-53461: In the Linux kernel, the following vulnerability has been resolved: io_uring: wait interruptibly for request completions on exit WHen the ring exits,
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 r
Red Hat
kernel: Linux kernel: Denial of Service in io_uring due to hung task detection
vendor_redhat·2025-10-01·CVSS 5.5
CVE-2023-53461 [MEDIUM] CWE-667 kernel: Linux kernel: Denial of Service in io_uring due to hung task detection
kernel: Linux kernel: Denial of Service in io_uring due to hung task detection
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 compl
Debian
CVE-2023-53461: linux - In the Linux kernel, the following vulnerability has been resolved: io_uring: w...
vendor_debian·2023·CVSS 5.5
CVE-2023-53461 [MEDIUM] CVE-2023-53461: linux - In the Linux kernel, the following vulnerability has been resolved: io_uring: w...
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 r
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/28e649dc9947e6525c95e32aa9a8e147925e3f56https://git.kernel.org/stable/c/4826c59453b3b4677d6bf72814e7ababdea86949https://git.kernel.org/stable/c/58e80cb68b057e974768792c34708c6957810486https://git.kernel.org/stable/c/8e29835366138389bfad3b31ea06960d0a77bf77https://git.kernel.org/stable/c/b50d6e06cca7b67a3d73ca660dda27662b76e6ea
2025-10-01
Published