CVE-2026-97619: Linux Vulnerability

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.

Metrics

EPSS Probability

0.21%

10.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= ea2e6286e3e89a115ae554e20ba9aec2b2e1ddff, < aa4a3bec32ffe20ba1044db8211140edf7637310; >= 89a410dbd0f159ddd308f19d6eb682fc753e4771, < 16840e3478c72ebbf093c52cbdcd8a1f12fad692; >= b000145e9907809406d8164c3b2b8861d95aecd1, < ed1cead97afb9c398bd7ab344a3c1ee34ab73af9; >= b000145e9907809406d8164c3b2b8861d95aecd1, < 696459029f3b65c070c91b729478475582f1dcdf; >= b000145e9907809406d8164c3b2b8861d95aecd1, < cc580cee4dfa2ec9099c30ecbd4d804cbb996432; >= b000145e9907809406d8164c3b2b8861d95aecd1, < 055d43a1233edbd80e558889258105ce63051bcd; >= b000145e9907809406d8164c3b2b8861d95aecd1, < 796aa0547557e63338657ed1c487906f9fac4c73; 2a853c206e553dd9c0a55c22858fd6a446d93e15; >= 5.10.165, < 5.10.273; >= 5.15.90, < 5.15.224; >= 6.0.3, < 6.1
Linux	Linux	6.1

References

Timeline

Published: Sep 25, 2026
Last Modified: Oct 30, 2026
Status: Received

Frequently Asked Questions

What is CVE-2026-97619?

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.

How severe is CVE-2026-97619?

Severity scoring for CVE-2026-97619 is pending analysis. The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.

How do I fix CVE-2026-97619?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →