Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 14b7ecad2ec56699325180a744f4b19f046401bb, 1636d85dc139b07c0449308f2bb5e0c7a2e0da99, 29bef9934b2521f787bb15dd1985d4c0d12ae02a; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1.

Low priority for now. Upgrade to Linux Linux 14b7ecad2ec56699325180a744f4b19f046401bb, 1636d85dc139b07c0449308f2bb5e0c7a2e0da99, 29bef9934b2521f787bb15dd1985d4c0d12ae02a; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jul 25, 2026
Updated
Oct 15, 2026
EPSS
0.1% · 2th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-64425

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.10.253 and later · before 5.10.261
  • linux linux kernel5.15.203 and later · before 5.15.212
  • linux linux kernel6.1.167 and later · before 6.1.178
  • linux linux kernel6.6.122 and later · before 6.6.145
  • linux linux kernel6.12.68 and later · before 6.12.96
  • linux linux kernel6.18.8 and later · before 6.18.39
  • linux linux kernel6.19.1 and later · before 7.1.4
  • linux linux kernel6.19

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.19affected
    • 6.12.96 and later · up to and including 6.12.*not affected · semver
    • 6.18.39 and later · up to and including 6.18.*not affected · semver
    • 7.1.4 and later · up to and including 7.1.*not affected · semver
    • 7.2 and laternot affected · original_commit_for_fix
    • 065dd936195a3466b8ebe5f9287400987ee3c063 and later · before 14b7ecad2ec56699325180a744f4b19f046401bbaffected · git
    • 27e47500fac23d15b7dc93ff650bc4844d2581bd and later · before d179533c610e1b4c6aa436e3c1fd1b719d2c727caffected · git
    • d05d99573f81a091547b1778b9a50120f5d6c68a and later · before 6e2f51f3e06773c2ee98ad09738f0908b48f76f9affected · git
    • 85eb83694a91c89d9abe615d717c0053c3efa714 and later · before ea61b04e1d7242cb37f5ed2cc91cf21a493f6597affected · git
    • 2e8ca1078b14142db2ce51cbd18ff9971560046b and later · before b6f179a653a934736c88d820fe0098c3c2532549affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:12linux-6.12before 6.12.100-1~deb12u16.12.100-1~deb12u1
Debian:13linuxbefore 6.12.96-16.12.96-1
Debian:14linuxbefore 7.1.4-17.1.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-64423Jul 25, 2026 · ipv4: igmp: remove multicast group from hash table on device destruction
    31Monitor
  • ← EarlierCVE-2026-64424Jul 25, 2026 · netpoll: fix a use-after-free on shutdown path
    31Monitor
  • Later →CVE-2026-64432Jul 25, 2026 · fs/ntfs3: validate Dirty Page Table capacity in log_replay copy_lcns
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux14b7ecad2ec56699325180a744f4b19f046401bbVendor (CNA)
Linux Linux1636d85dc139b07c0449308f2bb5e0c7a2e0da99Vendor (CNA)
Linux Linux29bef9934b2521f787bb15dd1985d4c0d12ae02aVendor (CNA)
Linux Linux5.10.261Vendor (CNA)
Linux Linux5.15.212Vendor (CNA)
Linux Linux6.1.178Vendor (CNA)
Linux Linux6.12.96Vendor (CNA)
Linux Linux6.18.39Vendor (CNA)
Linux Linux6.6.145Vendor (CNA)
Linux Linux6e2f51f3e06773c2ee98ad09738f0908b48f76f9Vendor (CNA)
Linux Linuxab85765cbe3258b43dc6729af0e6ce3a87a133d8Vendor (CNA)
Linux Linuxb6f179a653a934736c88d820fe0098c3c2532549Vendor (CNA)
Linux Linuxd179533c610e1b4c6aa436e3c1fd1b719d2c727cVendor (CNA)
Linux Linuxea61b04e1d7242cb37f5ed2cc91cf21a493f6597Vendor (CNA)
azl3 kernel 6.6.144.1-1 on Azure Linux 3.06.6.145.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records