CVE-2026-64571

UNRATEDCVSS · not yet scoredTrending — 5 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:

wifi: p54: validate RX frame length in p54_rx_eeprom_readback()

p54_rx_eeprom_readback() copies the requested EEPROM slice out of a device-supplied readback frame without checking that the skb actually holds that many bytes. Commit da1b9a55ff11 ("wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback()") closed the destination overflow by copying a fixed priv->eeprom_slice_size (and rejecting a mismatched advertised len), but the source side is still unbounded: nothing verifies the frame is long enough to supply that many bytes.

A malicious USB device can send a short frame whose advertised len matches priv->eeprom_slice_size while the payload is truncated. The equality check passes and memcpy() reads past the end of the skb, leaking adjacent heap:

BUG: KASAN: slab-out-of-bounds in p54_rx (drivers/net/wireless/intersil/p54/txrx.c:507) Read of size 1016 at addr ffff88800f077114 by task swapper/0/0 Call Trace: ... __asan_memcpy (mm/kasan/shadow.c:105) p54_rx (drivers/net/wireless/intersil/p54/txrx.c:507) p54u_rx_cb (drivers/net/wireless/intersil/p54/p54usb.c:163) __usb_hcd_giveback_urb (drivers/usb/core/hcd.c:1657) dummy_timer (drivers/usb/gadget/udc/dummy_hcd.c:2005) ...

The buggy address belongs to the object at ffff88800f0770c0 which belongs to the cache skbuff_small_head of size 704 The buggy address is located 84 bytes inside of allocated 704-byte region [ffff88800f0770c0, ffff88800f077380)

Check that the slice fits in the skb before copying.

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

August 5, 2026

Last Modified

August 19, 2026

References (8)

Vendor Advisories for CVE-2026-64571(2)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (500 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (338 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)6.12.101-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.6-1—

Data Freshness Timeline

(refreshed 20× in last 7d / 35× 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 22:55 UTCEPSS rescore
  2. 2026-08-19 17:27 UTCVendor advisory
  3. 2026-08-19 17:27 UTCGHSA enrichment
  4. 2026-08-19 17:21 UTCNVD update
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-19 16:56 UTCVendor advisory
  7. 2026-08-19 16:56 UTCGHSA enrichment
  8. 2026-08-19 16:43 UTCMITRE cvelistV5
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 05:42 UTCVendor advisory
  12. 2026-08-17 05:42 UTCGHSA enrichment
  13. 2026-08-17 05:25 UTCNVD update
  14. 2026-08-17 05:13 UTCVendor advisory
  15. 2026-08-17 05:13 UTCGHSA enrichment
  16. 2026-08-17 05:05 UTCMITRE cvelistV5
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-15 02:20 UTCVendor advisory
  19. 2026-08-15 02:20 UTCGHSA enrichment
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 20:21 UTCVendor advisory
  24. 2026-08-11 20:21 UTCGHSA enrichment
  25. 2026-08-11 00:00 UTCEPSS rescore
Show 10 more
  1. 2026-08-09 13:47 UTCEPSS rescore
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-08 14:20 UTCEG score recompute
  4. 2026-08-08 14:20 UTCGHSA enrichment
  5. 2026-08-06 13:47 UTCEPSS rescore
  6. 2026-08-05 19:17 UTCEPSS rescore
  7. 2026-08-05 19:17 UTCEPSS rescore
  8. 2026-08-05 08:20 UTCNVD update
  9. 2026-08-05 08:12 UTCEG score recompute
  10. 2026-08-05 08:10 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2026-64571?
CVE-2026-64571 is a publicly disclosed vulnerability published on August 5, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: p54: validate RX frame length in p54rxeeprom_readback() p54rxeeprom_readback() copies the requested EEPROM slice out of a device-supplied readback frame without checking that the skb actually holds that many bytes. Commit…
When was CVE-2026-64571 disclosed?
CVE-2026-64571 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64571 actively exploited?
CVE-2026-64571 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-64571?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64571, 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-64571

Explore →

Is Your Infrastructure Affected by CVE-2026-64571?

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

Start Free Scan →Browse All CVEs