Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64425io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64425, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 065dd936195a3466b8ebe5f9287400987ee3c063 – < 14b7ecad2ec56699325180a744f4b19f046401bb
    • affected 27e47500fac23d15b7dc93ff650bc4844d2581bd – < d179533c610e1b4c6aa436e3c1fd1b719d2c727c
    • affected d05d99573f81a091547b1778b9a50120f5d6c68a – < 6e2f51f3e06773c2ee98ad09738f0908b48f76f9
    • affected 85eb83694a91c89d9abe615d717c0053c3efa714 – < ea61b04e1d7242cb37f5ed2cc91cf21a493f6597
    • affected 2e8ca1078b14142db2ce51cbd18ff9971560046b – < b6f179a653a934736c88d820fe0098c3c2532549
    • affected bdf0bf73006ea8af9327cdb85cfdff4c23a5f966 – < 1636d85dc139b07c0449308f2bb5e0c7a2e0da99
    • affected 10dc959398175736e495f71c771f8641e1ca1907 – < ab85765cbe3258b43dc6729af0e6ce3a87a133d8
    • affected 10dc959398175736e495f71c771f8641e1ca1907 – < 29bef9934b2521f787bb15dd1985d4c0d12ae02a
    • affected 5.10.253 – < 5.10.261
    • affected 5.15.203 – < 5.15.212
    • affected 6.1.167 – < 6.1.178
    • affected 6.6.122 – < 6.6.145
    • affected 6.12.68 – < 6.12.96
    • affected 6.18.8 – < 6.18.39
  • Linux · Linux

    • affected 6.19
    • unaffected < 6.19
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64425 badge
[![CVE-2026-64425](https://cveledger.app/badge/CVE-2026-64425.svg)](https://cveledger.app/cve/CVE-2026-64425)

Record last updated .