io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item commit 10dc95939817 ("io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop") fixed the obvious case where io_worker_handle_work() took one exit-bit snapshot before draining pending work, but the fix stops one level too early. io_worker_handle_work() now re-checks IO_WQ_BIT_EXIT in its outer work run loop, yet it still snapshots that bit once before processing a whole dependent linked-work chain. If io_wq_exit_start() sets IO_WQ_BIT_EXIT after the first linked item has started, the remaining linked items can still reuse stale do_kill = false, skip IO_WQ_WORK_CANCEL, and continue running after exit has begun. Move the check further inside, so it covers linked items too. Note: this is a syzbot special as it loves setting up tons of slow linked work on weird devices like msr that take forever to read, and immediately close the ring. Exit then takes a long time.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 065dd936195a3466b8ebe5f9287400987ee3c063 · fixed in 14b7ecad2ec56699325180a744f4b19f046401bb; From 27e47500fac23d15b7dc93ff650bc4844d2581bd · fixed in d179533c610e1b4c6aa436e3c1fd1b719d2c727c; From d05d99573f81a091547b1778b9a50120f5d6c68a · fixed in 6e2f51f3e06773c2ee98ad09738f0908b48f76f9; From 85eb83694a91c89d9abe615d717c0053c3efa714 · fixed in ea61b04e1d7242cb37f5ed2cc91cf21a493f6597; From 2e8ca1078b14142db2ce51cbd18ff9971560046b · fixed in b6f179a653a934736c88d820fe0098c3c2532549; From bdf0bf73006ea8af9327cdb85cfdff4c23a5f966 · fixed in 1636d85dc139b07c0449308f2bb5e0c7a2e0da99; From 10dc959398175736e495f71c771f8641e1ca1907 · fixed in ab85765cbe3258b43dc6729af0e6ce3a87a133d8; From 10dc959398175736e495f71c771f8641e1ca1907 · fixed in 29bef9934b2521f787bb15dd1985d4c0d12ae02a; From 5.10.253 · fixed in 5.10.261; From 5.15.203 · fixed in 5.15.212; From 6.1.167 · fixed in 6.1.178; From 6.6.122 · fixed in 6.6.145; From 6.12.68 · fixed in 6.12.96; From 6.18.8 · fixed in 6.18.39
- Linux Linux
6.19
- KernelLinux
fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.96; From 6.13.0 · fixed in 6.18.39; From 6.19.0 · fixed in 7.1.4
References 8
git.kernel.org
- stable/c/14b7ecad2ec56699325180a744f4b19f046401bb
- stable/c/d179533c610e1b4c6aa436e3c1fd1b719d2c727c
- stable/c/6e2f51f3e06773c2ee98ad09738f0908b48f76f9
- stable/c/ea61b04e1d7242cb37f5ed2cc91cf21a493f6597
- stable/c/b6f179a653a934736c88d820fe0098c3c2532549
- stable/c/1636d85dc139b07c0449308f2bb5e0c7a2e0da99
- stable/c/ab85765cbe3258b43dc6729af0e6ce3a87a133d8
- stable/c/29bef9934b2521f787bb15dd1985d4c0d12ae02a