Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53461: io_uring: wait interruptibly for request completions on exit

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 28e649dc9947e6525c95e32aa9a8e147925e3f56, 4826c59453b3b4677d6bf72814e7ababdea86949, 58e80cb68b057e974768792c34708c6957810486.

Low priority for now. Upgrade to Linux Linux 28e649dc9947e6525c95e32aa9a8e147925e3f56, 4826c59453b3b4677d6bf72814e7ababdea86949, 58e80cb68b057e974768792c34708c6957810486 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Oct 1, 2025
Updated
Nov 5, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-53461

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.1affected
    • 2b188cc1bb857a9d4701ae59aa7768b5124e262e and later · before 28e649dc9947e6525c95e32aa9a8e147925e3f56affected · git
    • 2b188cc1bb857a9d4701ae59aa7768b5124e262e and later · before 8e29835366138389bfad3b31ea06960d0a77bf77affected · git
    • 2b188cc1bb857a9d4701ae59aa7768b5124e262e and later · before b50d6e06cca7b67a3d73ca660dda27662b76e6eaaffected · git
    • 2b188cc1bb857a9d4701ae59aa7768b5124e262e and later · before 58e80cb68b057e974768792c34708c6957810486affected · git
    • 2b188cc1bb857a9d4701ae59aa7768b5124e262e and later · before 4826c59453b3b4677d6bf72814e7ababdea86949affected · git
    • before 5.1not affected · semver
    • 5.10.188 and later · up to and including 5.10.*not affected · semver
    • 5.15.121 and later · up to and including 5.15.*not affected · semver
    • 6.1.39 and later · up to and including 6.1.*not affected · semver
Affected versions · NVD (4)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.1 and later · before 5.10.188
  • linux linux kernel5.11 and later · before 5.15.121
  • linux linux kernel5.16 and later · before 6.1.39
  • linux linux kernel6.2 and later · before 6.4.4

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.52-16.1.52-1
Debian:13linuxbefore 6.4.4-16.4.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-53458Oct 1, 2025 · media: cx23885: Fix a null-ptr-deref bug in buffer_prepare() and buffer_finish()
    22Monitor
  • ← EarlierCVE-2023-53460Oct 1, 2025 · wifi: rtw88: fix memory leak in rtw_usb_probe()
    22Monitor
  • Later →CVE-2023-53463Oct 1, 2025 · ibmvnic: Do not reset dql stats on NON_FATAL err
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux28e649dc9947e6525c95e32aa9a8e147925e3f56Vendor (CNA)
Linux Linux4826c59453b3b4677d6bf72814e7ababdea86949Vendor (CNA)
Linux Linux58e80cb68b057e974768792c34708c6957810486Vendor (CNA)
Linux Linux8e29835366138389bfad3b31ea06960d0a77bf77Vendor (CNA)
Linux Linuxb50d6e06cca7b67a3d73ca660dda27662b76e6eaVendor (CNA)
debian:linux6.1.52-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records