CVE-2026-64327

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:

usb: gadget: f_fs: Initialize epfile->in early to fix endpoint direction checks

When parsing endpoint descriptors, ffs_data_got_descs() generates the eps_addrmap which contains the endpoint direction. However, epfile->in was previously only populated in ffs_func_eps_enable() which executes upon USB host connection. As a result, early userspace ioctls like FUNCTIONFS_DMABUF_ATTACH that run before the host connects would see epfile->in as 0, leading to incorrect DMA directions.

By moving the initialization to ffs_epfiles_create(), epfile->in is accurate before userspace opens the endpoint files.

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

Published

July 25, 2026

Last Modified

August 17, 2026

Vendor Advisories for CVE-2026-64327(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
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 / 38× 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:10 UTCGHSA enrichment
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-26 14:47 UTCEPSS rescore
  5. 2026-08-26 06:51 UTCGHSA enrichment
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-23 06:00 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-20 05:40 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:25 UTCNVD update
  16. 2026-08-17 05:20 UTCGHSA enrichment
  17. 2026-08-17 05:05 UTCMITRE cvelistV5
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 15:28 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 15:08 UTCGHSA enrichment
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-10 04:32 UTCGHSA enrichment
Show 29 more
  1. 2026-08-09 13:47 UTCEPSS rescore
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-07 04:12 UTCGHSA enrichment
  4. 2026-08-06 13:47 UTCEPSS rescore
  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 03:52 UTCGHSA enrichment
  9. 2026-08-03 10:36 UTCEPSS rescore
  10. 2026-08-02 02:27 UTCEPSS rescore
  11. 2026-08-01 04:16 UTCEPSS rescore
  12. 2026-08-01 03:32 UTCEG score recompute
  13. 2026-08-01 03:32 UTCGHSA enrichment
  14. 2026-07-30 16:28 UTCEPSS rescore
  15. 2026-07-30 01:30 UTCEPSS rescore
  16. 2026-07-30 01:30 UTCEPSS rescore
  17. 2026-07-29 03:11 UTCEG score recompute
  18. 2026-07-29 03:10 UTCGHSA enrichment
  19. 2026-07-28 15:37 UTCEPSS rescore
  20. 2026-07-27 14:14 UTCEPSS rescore
  21. 2026-07-26 14:54 UTCEPSS rescore
  22. 2026-07-26 14:54 UTCEPSS rescore
  23. 2026-07-26 02:50 UTCEG score recompute
  24. 2026-07-26 02:50 UTCGHSA enrichment
  25. 2026-07-25 14:18 UTCEPSS rescore
  26. 2026-07-25 14:18 UTCEPSS rescore
  27. 2026-07-25 10:39 UTCNVD update
  28. 2026-07-25 09:37 UTCEG score recompute
  29. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-64327?
CVE-2026-64327 is a publicly disclosed vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Initialize epfile->in early to fix endpoint direction checks When parsing endpoint descriptors, ffsdatagot_descs() generates the eps_addrmap which contains the endpoint direction. However, epfile->in was…
When was CVE-2026-64327 disclosed?
CVE-2026-64327 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-64327 actively exploited?
CVE-2026-64327 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 89.5% of all scored CVEs.
How do I remediate CVE-2026-64327?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64327, 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-64327

Explore →

Is Your Infrastructure Affected by CVE-2026-64327?

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