Skip to content
Noroxi
CVE-2026-97619· NVD / CVE Program· CNA Linux

io_uring/rw: end write accounting from ->ki_complete

In the Linux kernel, the following vulnerability has been resolved: io_uring/rw: end write accounting from ->ki_complete Commit b000145e9907 moved both the fsnotify calls and the write accounting out of the kiocb completion handler and into the io_req_rw_complete() task_work. However, only the fsnotify part actually needed to move as it may sleep. Ending the write accounting is just a percpu_up_read() on the superblock writers sem. Deferring it is a problem, because it makes dropping SB_FREEZE_WRITE protection depend on the ring owner getting to running task_work. But the task may be blocked in freeze_super(), causing it to never get to that: task io-wq worker -------------------------------------------------------------- io_write() io_kiocb_start_write() (takes sb_writers, hidden from lockdep by __sb_writers_release) write_iter() -> -EIOCBQUEUED ioctl(FS_IOC_SHUTDOWN) bdev_freeze() freeze_super() percpu_down_write() <- waits for the reader above io_write() kiocb_start_write() percpu_down_read() <- queued behind the writer <bio completes> io_complete_rw() queues io_req_rw_complete() <- never runs, task is in D state End the write from io_complete_rw() instead, and leave only the fsnotify calls in task_work.

—No exploit Fix available
Published
Sep 25, 2026
Updated
Oct 3, 2026
EPSS
0.2% · 9th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

—

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

    • ea2e6286e3e89a115ae554e20ba9aec2b2e1ddff, 89a410dbd0f159ddd308f19d6eb682fc753e4771, 2a853c206e553dd9c0a55c22858fd6a446d93e15, 6.1affected
    • b000145e9907809406d8164c3b2b8861d95aecd1 and later · before 696459029f3b65c070c91b729478475582f1dcdfaffected · git
    • b000145e9907809406d8164c3b2b8861d95aecd1 and later · before cc580cee4dfa2ec9099c30ecbd4d804cbb996432affected · git
    • b000145e9907809406d8164c3b2b8861d95aecd1 and later · before 055d43a1233edbd80e558889258105ce63051bcdaffected · git
    • b000145e9907809406d8164c3b2b8861d95aecd1 and later · before 796aa0547557e63338657ed1c487906f9fac4c73affected · git
    • 5.10.165 and later · before 5.11affected · semver
    • 5.15.90 and later · before 5.16affected · semver
    • 6.0.3 and later · before 6.1affected · semver
    • before 6.1not affected · semver
    • 6.12.112 and later · up to and including 6.12.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxall versions—
Debian:14linuxbefore 7.2.7-17.2.7-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan
  • CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler
    40Plan
  • CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
    40Plan
  • CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index
    40Plan

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 Linux055d43a1233edbd80e558889258105ce63051bcdVendor (CNA)
Linux Linux5.11Vendor (CNA)
Linux Linux5.16Vendor (CNA)
Linux Linux6.1Vendor (CNA)
Linux Linux696459029f3b65c070c91b729478475582f1dcdfVendor (CNA)
Linux Linux796aa0547557e63338657ed1c487906f9fac4c73Vendor (CNA)
Linux Linuxcc580cee4dfa2ec9099c30ecbd4d804cbb996432Vendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
debian:linux7.2.7-1 · Debian:14Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

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

All records