CVE-2026-64544

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

crypto: asymmetric_keys - fix OOB read in pefile_digest_pe_contents

pefile_digest_pe_contents() computes the trailing-data hash length as pelen - (hashed_bytes + certs_size). A crafted PE can make the addition exceed pelen, causing the unsigned subtraction to underflow to ~4 GiB. This is passed to crypto_shash_update() which reads out of bounds and panics on unmapped vmalloc guard pages.

BUG: unable to handle page fault for address: ffffc900038d8000 Oops: Oops: 0000 [#1] SMP KASAN NOPTI RIP: 0010:sha256_blocks_generic (lib/crypto/sha256.c:152) Call Trace: __sha256_update (lib/crypto/sha256.c:208) crypto_sha256_update (crypto/sha256.c:142) verify_pefile_signature (crypto/asymmetric_keys/verify_pefile.c:436) kexec_kernel_verify_pe_sig (kernel/kexec_file.c:151) __do_sys_kexec_file_load (kernel/kexec_file.c:406) do_syscall_64 (arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) Kernel panic - not syncing: Fatal exception

Validate that the addition does not overflow and the result does not exceed pelen before the subtraction. Return -ELIBBAD on failure.

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

Published

July 27, 2026

Last Modified

August 17, 2026

Vendor Advisories for CVE-2026-64544(1)

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

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)6.12.100-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (157 versions)7.1.5-1

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Frequently asked(4)

What is CVE-2026-64544?
CVE-2026-64544 is a publicly disclosed vulnerability published on July 27, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: asymmetrickeys - fix OOB read in pefiledigestpecontents pefiledigestpe_contents() computes the trailing-data hash length as pelen - (hashedbytes + certssize). A crafted PE can make the addition exceed pelen, causing the…
When was CVE-2026-64544 disclosed?
CVE-2026-64544 was first published in the National Vulnerability Database on July 27, 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-64544 actively exploited?
CVE-2026-64544 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 92.7% of all scored CVEs.
How do I remediate CVE-2026-64544?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64544, 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-64544

Explore →

Is Your Infrastructure Affected by CVE-2026-64544?

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