CVE-2026-64426

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

io_uring/nop: fix file reference leak with IOSQE_FIXED_FILE

NOP file-acquisition support choses between a fixed (registered) file and a normal fget()'d file based on its own IORING_NOP_FIXED_FILE flag in sqe->nop_flags. However, a request's REQ_F_FIXED_FILE is set independently from the generic IOSQE_FIXED_FILE sqe flag during request init, before the issue handler runs.

If a NOP is submitted with IOSQE_FIXED_FILE set (so REQ_F_FIXED_FILE is set) but without IORING_NOP_FIXED_FILE, io_nop() takes the normal path and grabs a real reference via io_file_get_normal(). On completion, io_put_file() only drops the reference when REQ_F_FIXED_FILE is clear, so the fget()'d file is never released and leaks:

BUG: memory leak unreferenced object 0xffff88800f42c240 (size 176): kmem_cache_alloc_noprof+0x358/0x440 alloc_empty_file+0x57/0x180 path_openat+0x44/0x1e50 do_file_open+0x121/0x200 do_sys_openat2+0xa7/0x150 __x64_sys_openat+0x82/0xf0

Decide between fixed and normal file acquisition from REQ_F_FIXED_FILE, the same way io_assign_file() does for every other opcode, and fold IORING_NOP_FIXED_FILE into REQ_F_FIXED_FILE at prep time.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

References (3)

Vendor Advisories for CVE-2026-64426(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1—

Data Freshness Timeline

(refreshed 6× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:04 UTCGHSA enrichment
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-26 14:47 UTCEPSS rescore
  5. 2026-08-25 15:52 UTCGHSA enrichment
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 20:30 UTCGHSA enrichment
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-20 01:07 UTCGHSA enrichment
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 05:43 UTCGHSA enrichment
  16. 2026-08-17 05:25 UTCNVD update
  17. 2026-08-17 05:17 UTCGHSA enrichment
  18. 2026-08-17 05:05 UTCMITRE cvelistV5
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 10:28 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 15:06 UTCGHSA enrichment
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-09 13:47 UTCEPSS rescore
Show 30 more
  1. 2026-08-09 03:48 UTCGHSA enrichment
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-06 13:47 UTCEPSS rescore
  4. 2026-08-06 08:25 UTCGHSA enrichment
  5. 2026-08-05 19:17 UTCEPSS rescore
  6. 2026-08-05 19:17 UTCEPSS rescore
  7. 2026-08-04 15:10 UTCEPSS rescore
  8. 2026-08-04 10:39 UTCEPSS rescore
  9. 2026-08-03 13:02 UTCGHSA enrichment
  10. 2026-08-03 10:36 UTCEPSS rescore
  11. 2026-08-02 02:27 UTCEPSS rescore
  12. 2026-08-01 04:16 UTCEPSS rescore
  13. 2026-07-31 17:39 UTCEG score recompute
  14. 2026-07-31 17:39 UTCGHSA enrichment
  15. 2026-07-30 16:28 UTCEPSS rescore
  16. 2026-07-30 01:30 UTCEPSS rescore
  17. 2026-07-30 01:30 UTCEPSS rescore
  18. 2026-07-28 22:13 UTCEG score recompute
  19. 2026-07-28 22:13 UTCGHSA enrichment
  20. 2026-07-28 15:37 UTCEPSS rescore
  21. 2026-07-27 14:14 UTCEPSS rescore
  22. 2026-07-26 14:54 UTCEPSS rescore
  23. 2026-07-26 14:54 UTCEPSS rescore
  24. 2026-07-26 02:47 UTCEG score recompute
  25. 2026-07-26 02:47 UTCGHSA enrichment
  26. 2026-07-25 14:18 UTCEPSS rescore
  27. 2026-07-25 14:18 UTCEPSS rescore
  28. 2026-07-25 10:39 UTCNVD update
  29. 2026-07-25 09:29 UTCEG score recompute
  30. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-64426?
CVE-2026-64426 is a publicly disclosed vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: iouring/nop: fix file reference leak with IOSQEFIXED_FILE NOP file-acquisition support choses between a fixed (registered) file and a normal fget()'d file based on its own IORINGNOPFIXED_FILE flag in sqe->nopflags. However, a…
When was CVE-2026-64426 disclosed?
CVE-2026-64426 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64426 actively exploited?
CVE-2026-64426 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.9% of all scored CVEs.
How do I remediate CVE-2026-64426?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64426, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64426

Explore →

Is Your Infrastructure Affected by CVE-2026-64426?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs