VulnerabilityPublished 25 Sep 2026Updated 30 Oct 2026

CVE-2026-97619: Linux kernel · io_uring/rw: end write accounting from ->ki_complete

Source GCVE Database

Compare

Authoritative record:CVE-2026-97619· High

Not known to be exploited · fixed in ed1cead97afb9c398bd7ab344a3c1ee34ab73af9 : patch Linux kernel soon.

Data as of 30 Oct 2026, 17:20 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in ed1cead97afb9c398bd7ab344a3c1ee34ab73af9, cc580cee4dfa2ec9099c30ecbd4d804cbb996432, aa4a3bec32ffe20ba1044db8211140edf7637310 +7

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-rr3w-gg4f-957r

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=5.10.165 <5.10.273 >=5.15.90 <5.15.224 >=6.0.3 <6.1	Fixed in ed1cead97afb9c398bd7ab344a3c1ee34ab73af9 cc580cee4dfa2ec9099c30ecbd4d804cbb996432 aa4a3bec32ffe20ba1044db8211140edf7637310 696459029f3b65c070c91b729478475582f1dcdf 16840e3478c72ebbf093c52cbdcd8a1f12fad692 796aa0547557e63338657ed1c487906f9fac4c73 055d43a1233edbd80e558889258105ce63051bcd 6.1 5.15.224 5.10.273
LinuxLinux	Affected =6.1	Fixed in–

AI-suggested

A fix has been implemented in the Linux kernel by moving the end of write accounting back to the io_complete_rw() context. Users should update to a kernel version that includes this fix once available. Until then, avoiding scenarios that trigger filesystem freeze during io_uring writes may reduce risk, but no official workaround is documented.

Description

CVE-2026-97619 is a vulnerability in the Linux kernel's io_uring subsystem related to write accounting. The issue arises because write accounting was deferred to task_work, which may never run if the task is blocked in freeze_super(), causing a deadlock scenario. This was fixed by moving the end of write accounting back to the io_complete_rw() context, ensuring proper release of write locks.

Impact

This flaw can cause a deadlock in the Linux kernel when io_uring write operations coincide with filesystem freeze operations (FS_IOC_SHUTDOWN). The deadlock occurs because the write accounting release depends on task_work execution, which may be blocked, preventing the release of the superblock writers semaphore and potentially causing system hangs or unresponsiveness during shutdown or freeze operations.

References

Community reviews

Loading reviews…