Answer in brief
CVE-2026-97619 records a Unknown severity vulnerability in io_uring/rw: end write accounting from ->ki_complete. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b000145e9907809406d8164c3b2b8861d95aecd1 <cc580cee4dfa2ec9099c30ecbd4d804cbb996432 || >=b000145e9907809406d8164c3b2b8861d95aecd1 <055d43a1233edbd80e558889258105ce63051bcd || >=b000145e9907809406d8164c3b2b8861d95aecd1 <796aa0547557e63338657ed1c487906f9fac4c73 || ea2e6286e3e89a115ae554e20ba9aec2b2e1ddff || 89a410dbd0f159ddd308f19d6eb682fc753e4771 || 2a853c206e553dd9c0a55c22858fd6a446d93e15 || >=5.10.165 <5.11 || >=5.15.90 <5.16 || >=6.0.3 <6.1 | cc580cee4dfa2ec9099c30ecbd4d804cbb996432, 055d43a1233edbd80e558889258105ce63051bcd, 796aa0547557e63338657ed1c487906f9fac4c73, 5.11, 5.16, 6.1 |
| Linux/Linuxgeneric | 6.1 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.