CVE-2026-64596

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
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:

libfs: set SB_I_NOEXEC and SB_I_NODEV by default in init_pseudo()

Since commit 1e7ab6f67824 ("anon_inode: rework assertions"), path_noexec() warns when an anonymous-inode file is mmap'd from a superblock that has not set SB_I_NOEXEC. dma-buf backs its files this way and never set the flag, so mmap of any exported buffer trips the warning on a CONFIG_DEBUG_VFS=y kernel:

WARNING: CPU: 11 PID: 121813 at fs/exec.c:118 path_noexec+0x47/0x50 do_mmap+0x2b5/0x680 vm_mmap_pgoff+0x129/0x210 ksys_mmap_pgoff+0x177/0x240 __x64_sys_mmap+0x33/0x70

init_pseudo() sets up internal SB_NOUSER mounts that are never path-reachable. Set both flags here so every pseudo filesystem gets them by default instead of each caller setting them.

SB_I_NODEV is inert for unreachable mounts. SB_I_NOEXEC has one visible effect: an executable mapping of a pseudo-fs fd, such as a dma-buf, now fails with -EPERM, which is the invariant the assertion enforces. No in-tree caller maps these executable.

Reproduce on CONFIG_DEBUG_VFS=y:

make -C tools/testing/selftests/dmabuf-heaps sudo ./tools/testing/selftests/dmabuf-heaps/dmabuf-heap -t system

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
5%
KEV
Not listed

Published

August 6, 2026

Last Modified

August 17, 2026

References (3)

Vendor Advisories for CVE-2026-64596(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 12× in last 7d / 23× 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-20 05:28 UTCGHSA enrichment
  2. 2026-08-19 17:04 UTCEPSS rescore
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-17 05:41 UTCGHSA enrichment
  6. 2026-08-17 05:25 UTCNVD update
  7. 2026-08-17 05:13 UTCGHSA enrichment
  8. 2026-08-17 05:05 UTCMITRE cvelistV5
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-15 07:41 UTCGHSA enrichment
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-12 13:51 UTCEPSS rescore
  14. 2026-08-12 07:54 UTCGHSA enrichment
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-09 13:47 UTCEPSS rescore
  17. 2026-08-09 08:08 UTCEG score recompute
  18. 2026-08-09 08:08 UTCGHSA enrichment
  19. 2026-08-08 16:37 UTCEPSS rescore
  20. 2026-08-06 13:47 UTCEPSS rescore
  21. 2026-08-06 08:21 UTCNVD update
  22. 2026-08-06 07:25 UTCEG score recompute
  23. 2026-08-06 07:25 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-64596?
CVE-2026-64596 is a publicly disclosed vulnerability published on August 6, 2026. In the Linux kernel, the following vulnerability has been resolved: libfs: set SBINOEXEC and SBINODEV by default in init_pseudo() Since commit 1e7ab6f67824 ("anon_inode: rework assertions"), path_noexec() warns when an anonymous-inode file is mmap'd from a superblock that has not set SBINOEXEC.…
When was CVE-2026-64596 disclosed?
CVE-2026-64596 was first published in the National Vulnerability Database on August 6, 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-64596 actively exploited?
CVE-2026-64596 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 94.9% of all scored CVEs.
How do I remediate CVE-2026-64596?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64596, 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-64596

Explore →

Is Your Infrastructure Affected by CVE-2026-64596?

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

Start Free Scan →Browse All CVEs