Strix
26.1K

CVE-2026-64425

UnknownEPSS 0.18%

Last modified

CVE-2026-64425 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
0.18%

7.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

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

VendorProductVersions
LinuxLinux>= 065dd936195a3466b8ebe5f9287400987ee3c063, < 14b7ecad2ec56699325180a744f4b19f046401bb; >= 27e47500fac23d15b7dc93ff650bc4844d2581bd, < d179533c610e1b4c6aa436e3c1fd1b719d2c727c; >= d05d99573f81a091547b1778b9a50120f5d6c68a, < 6e2f51f3e06773c2ee98ad09738f0908b48f76f9; >= 85eb83694a91c89d9abe615d717c0053c3efa714, < ea61b04e1d7242cb37f5ed2cc91cf21a493f6597; >= 2e8ca1078b14142db2ce51cbd18ff9971560046b, < b6f179a653a934736c88d820fe0098c3c2532549; >= bdf0bf73006ea8af9327cdb85cfdff4c23a5f966, < 1636d85dc139b07c0449308f2bb5e0c7a2e0da99; >= 10dc959398175736e495f71c771f8641e1ca1907, < ab85765cbe3258b43dc6729af0e6ce3a87a133d8; >= 10dc959398175736e495f71c771f8641e1ca1907, < 29bef9934b2521f787bb15dd1985d4c0d12ae02a; >= 5.10.253, < 5.10.261; >= 5.15.203, < 5.15.212; >= 6.1.167, < 6.1.178; >= 6.6.122, < 6.6.145; >= 6.12.68, < 6.12.96; >= 6.18.8, < 6.18.39
LinuxLinux6.19

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is CVE-2026-64425?
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.
How severe is CVE-2026-64425?
Severity scoring for CVE-2026-64425 is pending analysis. The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2026-64425?
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 →

Are you affected by CVE-2026-64425?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST