CVE-2026-64323

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1EG
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.1Exploit: 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 VAT header length against the VAT inode size

udf_load_vat() takes the virtual partition's start offset straight from the on-disk VAT 2.0 header without checking it against the VAT inode size:

map->s_type_specific.s_virtual.s_start_offset = le16_to_cpu(vat20->lengthHeader); map->s_type_specific.s_virtual.s_num_entries = (sbi->s_vat_inode->i_size - map->s_type_specific.s_virtual.s_start_offset) >> 2;

lengthHeader is a fully attacker-controlled 16-bit value. If it exceeds the VAT inode size, the s_num_entries subtraction underflows to a huge count, which defeats the "block > s_num_entries" bound in udf_get_pblock_virt15(); and on the ICB-inline path that function reads

((__le32 *)(iinfo->i_data + s_start_offset))[block]

so a large s_start_offset indexes past the inode's in-ICB data. Mounting a crafted UDF image with a virtual (VAT) partition then triggers an out-of-bounds read.

Reject a VAT whose header length does not leave room for at least one entry within the VAT inode.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 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 VAT header length against the VAT inode size - kernel/git/stable/linux.git - Linux kernel stable tree

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

udf: validate VAT header length against the VAT inode size - kernel/git/stable/linux.git - Linux kernel stable tree

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

udf: validate VAT header length against the VAT inode size - kernel/git/stable/linux.git - Linux kernel stable tree

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

udf: validate VAT header length against the VAT inode size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/883962731420ec271ed8c1cd76524f4b17faa982
generic

udf: validate VAT header length against the VAT inode size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/74580fdf022909e184223cacc364feb826982d96
generic

udf: validate VAT header length against the VAT inode size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/55287a3555ff0515b3aff181d2c08c0462a41709
generic

udf: validate VAT header length against the VAT inode size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2900e02a0dd4fc30ac9840e7ce4ca0b041ab0d63
generic

udf: validate VAT header length against the VAT inode size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0ad2d09a8d66fa8dc6f9b70d660b5fb4478ea934

Vendor Advisories for CVE-2026-64323(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 / 148× 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 176 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64323?
CVE-2026-64323 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: udf: validate VAT header length against the VAT inode size udfloadvat() takes the virtual partition's start offset straight from the on-disk VAT 2.0 header without checking it against the VAT inode size:…
When was CVE-2026-64323 disclosed?
CVE-2026-64323 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-64323 actively exploited?
CVE-2026-64323 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64323?
CVE-2026-64323 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-64323?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64323, 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-64323

Explore →

Is Your Infrastructure Affected by CVE-2026-64323?

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