Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2023-53461 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

io_uring: wait interruptibly for request completions on exit

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.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: None.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2023-53461 is recorded against 2 packages.

  • kernel (from 6.2.0 up to 6.4.4)
  • linux-kernel (from 6.2 up to 6.4.4)

Timeline and source

Published on 1 October 2025 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

CVE-2023-53461 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2025-10-01
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 6.2.0 6.4.4
linux-kernel 6.2 6.4.4

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2023-53461 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2023
✓