io_uring/rw: end write accounting from ->ki_complete
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel aa4a3bec32ffe20ba1044db8211140edf7637310, Kernel 6.1, Kernel 16840e3478c72ebbf093c52cbdcd8a1f12fad692 and 11 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=ea2e6286e3e89a115ae554e20ba9aec2b2e1ddff <aa4a3bec32ffe20ba1044db8211140edf7637310, >=6.0.3 <6.1, >=89a410dbd0f159ddd308f19d6eb682fc753e4771 <16840e3478c72ebbf093c52cbdcd8a1f12fad692, >=b000145e9907809406d8164c3b2b8861d95aecd1 <055d43a1233edbd80e558889258105ce63051bcd, >=b000145e9907809406d8164c3b2b8861d95aecd1 <696459029f3b65c070c91b729478475582f1dcdf, >=b000145e9907809406d8164c3b2b8861d95aecd1 <796aa0547557e63338657ed1c487906f9fac4c73, >=b000145e9907809406d8164c3b2b8861d95aecd1 <cc580cee4dfa2ec9099c30ecbd4d804cbb996432, >=b000145e9907809406d8164c3b2b8861d95aecd1 <ed1cead97afb9c398bd7ab344a3c1ee34ab73af9, =2a853c206e553dd9c0a55c22858fd6a446d93e15, =6.1, >=5.10.165 <5.10.273, >=5.15.90 <5.15.224 | aa4a3bec32ffe20ba1044db8211140edf7637310, 6.1, 16840e3478c72ebbf093c52cbdcd8a1f12fad692, 055d43a1233edbd80e558889258105ce63051bcd, 696459029f3b65c070c91b729478475582f1dcdf, 796aa0547557e63338657ed1c487906f9fac4c73, cc580cee4dfa2ec9099c30ecbd4d804cbb996432, ed1cead97afb9c398bd7ab344a3c1ee34ab73af9, 5.10.273, 5.15.224 |
| linux-kernel: Kernel | >=5.15.90 <5.15.224, >=6.0.3 <6.1, >=6.1.0 <6.6.160, >=6.13.0 <6.18.53, >=6.19.0 <7.2.7, >=6.7.0 <6.12.112, >=5.10.165 <5.10.273 | 5.15.224, 6.1, 6.6.160, 6.18.53, 7.2.7, 6.12.112, 5.10.273 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket