CVE-2026-64322

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: 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:

udf: validate sparing table length as an entry count, not a byte count

udf_load_sparable_map() accepts a sparing table when

sizeof(*st) + le16_to_cpu(st->reallocationTableLen) > sb->s_blocksize

is false, i.e. it treats reallocationTableLen as a number of BYTES that must fit in the block. But the table is walked as an array of 8-byte sparingEntry elements:

for (i = 0; i < le16_to_cpu(st->reallocationTableLen); i++) { struct sparingEntry *entry = &st->mapEntry[i]; ... entry->origLocation ... }

in udf_get_pblock_spar15() and udf_relocate_blocks(). A reallocationTableLen of N therefore passes the check whenever sizeof(*st) + N <= blocksize, yet the consumers index sizeof(*st) + N * sizeof(struct sparingEntry) bytes -- up to ~8x the block. On a crafted UDF image this is an out-of-bounds read in udf_get_pblock_spar15(); udf_relocate_blocks() additionally feeds the same length to udf_update_tag(), whose crc_itu_t() reads far past the block, and its memmove() through st->mapEntry[] is an out-of-bounds write.

Validate reallocationTableLen as the entry count it is, with struct_size().

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

udf: validate sparing table length as an entry count, not a byte count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eeb0f3e193f8e523d03e4c9e084f6b4875f50e8e
generic

udf: validate sparing table length as an entry count, not a byte count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7f7774b9da0ef17b87bfa238cf966ad0b3376150
generic

udf: validate sparing table length as an entry count, not a byte count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7285276aa50d2839afb5957ffd491ad282dc8f72
generic

udf: validate sparing table length as an entry count, not a byte count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3ec997bd5508e9b25210b5bbec89031629cdb093
generic

udf: validate sparing table length as an entry count, not a byte count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2d726135099313958f8975532a2e15322ff150ce
generic

udf: validate sparing table length as an entry count, not a byte count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a219acb2ce674d99bbd1b7b35ed8c384dac7200
generic

udf: validate sparing table length as an entry count, not a byte count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0a9b79a951cfd70a9d31ca01ae2d08a20bb730e9
generic

udf: validate sparing table length as an entry count, not a byte count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/04f4599a9efb90992d072a814960edf0cd62805d

Vendor Advisories for CVE-2026-64322(2)

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.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 33× in last 7d / 146× 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.

Showing the most recent 100 of 174 total refreshes for this CVE.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:10 UTCEG score recompute
  3. 2026-08-30 00:10 UTCVendor advisory
  4. 2026-08-30 00:10 UTCGHSA enrichment
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 23:21 UTCEG score recompute
  7. 2026-08-27 23:21 UTCVendor advisory
  8. 2026-08-27 23:21 UTCGHSA enrichment
  9. 2026-08-27 11:10 UTCVendor advisory
  10. 2026-08-27 11:10 UTCGHSA enrichment
  11. 2026-08-26 22:58 UTCEG score recompute
  12. 2026-08-26 22:58 UTCVendor advisory
  13. 2026-08-26 22:58 UTCGHSA enrichment
  14. 2026-08-26 14:47 UTCEPSS rescore
  15. 2026-08-26 10:47 UTCVendor advisory
  16. 2026-08-26 10:47 UTCGHSA enrichment
  17. 2026-08-25 22:36 UTCEG score recompute
  18. 2026-08-25 22:36 UTCVendor advisory
  19. 2026-08-25 22:36 UTCGHSA enrichment
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 10:24 UTCVendor advisory
  22. 2026-08-25 10:24 UTCGHSA enrichment
  23. 2026-08-24 22:12 UTCEG score recompute
  24. 2026-08-24 22:12 UTCVendor advisory
  25. 2026-08-24 22:12 UTCGHSA enrichment
Show 75 more
  1. 2026-08-24 10:01 UTCEG score recompute
  2. 2026-08-24 10:01 UTCVendor advisory
  3. 2026-08-24 10:01 UTCGHSA enrichment
  4. 2026-08-23 21:50 UTCVendor advisory
  5. 2026-08-23 21:50 UTCGHSA enrichment
  6. 2026-08-23 09:39 UTCEG score recompute
  7. 2026-08-23 09:39 UTCVendor advisory
  8. 2026-08-23 09:39 UTCGHSA enrichment
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 21:28 UTCVendor advisory
  11. 2026-08-22 21:28 UTCGHSA enrichment
  12. 2026-08-22 09:17 UTCEG score recompute
  13. 2026-08-22 09:17 UTCVendor advisory
  14. 2026-08-22 09:17 UTCGHSA enrichment
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 21:06 UTCGHSA enrichment
  17. 2026-08-21 08:54 UTCEG score recompute
  18. 2026-08-21 08:54 UTCVendor advisory
  19. 2026-08-21 08:54 UTCGHSA enrichment
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 20:39 UTCVendor advisory
  22. 2026-08-20 20:39 UTCGHSA enrichment
  23. 2026-08-20 08:26 UTCVendor advisory
  24. 2026-08-20 08:26 UTCGHSA enrichment
  25. 2026-08-19 20:15 UTCEG score recompute
  26. 2026-08-19 20:15 UTCVendor advisory
  27. 2026-08-19 20:15 UTCGHSA enrichment
  28. 2026-08-19 17:04 UTCEPSS rescore
  29. 2026-08-19 07:02 UTCVendor advisory
  30. 2026-08-19 07:01 UTCGHSA enrichment
  31. 2026-08-18 18:50 UTCEG score recompute
  32. 2026-08-18 18:50 UTCVendor advisory
  33. 2026-08-18 18:50 UTCGHSA enrichment
  34. 2026-08-18 13:48 UTCEPSS rescore
  35. 2026-08-18 05:42 UTCGHSA enrichment
  36. 2026-08-17 17:31 UTCEG score recompute
  37. 2026-08-17 17:31 UTCVendor advisory
  38. 2026-08-17 17:31 UTCGHSA enrichment
  39. 2026-08-17 13:47 UTCEPSS rescore
  40. 2026-08-17 05:20 UTCEG score recompute
  41. 2026-08-17 05:20 UTCVendor advisory
  42. 2026-08-17 05:20 UTCGHSA enrichment
  43. 2026-08-16 17:00 UTCEG score recompute
  44. 2026-08-16 17:00 UTCVendor advisory
  45. 2026-08-16 17:00 UTCGHSA enrichment
  46. 2026-08-16 14:56 UTCEPSS rescore
  47. 2026-08-16 04:49 UTCEG score recompute
  48. 2026-08-16 04:49 UTCVendor advisory
  49. 2026-08-16 04:49 UTCGHSA enrichment
  50. 2026-08-15 16:38 UTCVendor advisory
  51. 2026-08-15 16:38 UTCGHSA enrichment
  52. 2026-08-15 04:27 UTCEG score recompute
  53. 2026-08-15 04:27 UTCVendor advisory
  54. 2026-08-15 04:27 UTCGHSA enrichment
  55. 2026-08-15 01:30 UTCEPSS rescore
  56. 2026-08-14 16:15 UTCVendor advisory
  57. 2026-08-14 16:15 UTCGHSA enrichment
  58. 2026-08-14 04:04 UTCEG score recompute
  59. 2026-08-14 04:04 UTCVendor advisory
  60. 2026-08-14 04:04 UTCGHSA enrichment
  61. 2026-08-13 22:00 UTCEPSS rescore
  62. 2026-08-13 15:53 UTCVendor advisory
  63. 2026-08-13 15:53 UTCGHSA enrichment
  64. 2026-08-13 03:42 UTCGHSA enrichment
  65. 2026-08-12 15:31 UTCEG score recompute
  66. 2026-08-12 15:31 UTCVendor advisory
  67. 2026-08-12 15:31 UTCGHSA enrichment
  68. 2026-08-12 13:51 UTCEPSS rescore
  69. 2026-08-12 03:20 UTCVendor advisory
  70. 2026-08-12 03:20 UTCGHSA enrichment
  71. 2026-08-11 15:08 UTCEG score recompute
  72. 2026-08-11 15:08 UTCVendor advisory
  73. 2026-08-11 15:08 UTCGHSA enrichment
  74. 2026-08-11 03:20 UTCEG score recompute
  75. 2026-08-11 03:20 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-64322?
CVE-2026-64322 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: udf: validate sparing table length as an entry count, not a byte count udfloadsparable_map() accepts a sparing table when sizeof(*st) + le16tocpu(st->reallocationTableLen) > sb->s_blocksize is false, i.e. it treats…
When was CVE-2026-64322 disclosed?
CVE-2026-64322 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-64322 actively exploited?
CVE-2026-64322 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64322?
CVE-2026-64322 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64322?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64322, 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-64322

Explore →

Is Your Infrastructure Affected by CVE-2026-64322?

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