--- cve: "CVE-2026-64425" severity: "LOW" cvss: 3.1 epss: "18%" vendor: "Linux" kev: false exploited: false published: "2026-07-25 10:17:26" tags: [cve, security, low] source: tsecurity.de CVE-Dossier exported: "2026-09-05T15:49:19+02:00" --- # CVE-2026-64425 > 3.1 LOW ## Beschreibung 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. ## Patch verfügbar (OSV) - Kernel ≥ 5.10.261 - Kernel ≥ 5.15.212 - Kernel ≥ 6.1.178 - Kernel ≥ 6.6.145 - Kernel ≥ 6.12.96 - Kernel ≥ 6.18.39 - Kernel ≥ 7.1.4 ## Referenzen - - - - - - - - --- _Exportiert aus dem [tsecurity.de CVE-Dossier](https://tsecurity.de/cve?cve=CVE-2026-64425) · Datenquellen: EUVD (ENISA), NVD, OSV, CISA KEV, FIRST EPSS, Exploit-DB, BSI BITS_