CVE-2026-64091

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.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: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

batman-adv: tt: fix TOCTOU race for reported vlans

The local TT based TVLV is generated by first checking the number of VLANs which have at least one TT entry. A new buffer with the correct size for the VLANs is then allocated. Only then, the list of VLANs s used to fill the VLAN entries in the buffer. During this time, the meshif_vlan_list_lock is held. But the actual number of TT entries of each VLAN can still increase during this time - just not the number of VLANs in the list.

But the prefilter used in the buffer size calculation might still cause an increase of the number of VLANs which need to be stored. Simply because a VLAN might now suddenly have at least one entry when it had none in the pre-alloc check - and then needs to occupy space which was not allocated.

It is better to overestimate the buffer size at the beginning and then fill the buffer only with the VLANs which are not empty.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 11, 2026

Advisory Details (8)

Auto-updated Aug 25, 2026
No patch confirmed yet.
generic

batman-adv: tt: fix TOCTOU race for reported vlans - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: tt: fix TOCTOU race for reported vlans - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: tt: fix TOCTOU race for reported vlans - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9a9c859457bc440a55773e01ff18b1bb5bab6836
generic

batman-adv: tt: fix TOCTOU race for reported vlans - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/94d27005016be15ffc638b2ecbc4d58805ad7b48
generic

batman-adv: tt: fix TOCTOU race for reported vlans - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/724a8eb4155669797c96b70d70e354284ae3b5a8
generic

batman-adv: tt: fix TOCTOU race for reported vlans - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/65a1e67339aa8c95ac544b796946af388930ee23
generic

batman-adv: tt: fix TOCTOU race for reported vlans - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4cc85aec8d3c9ab4dc716dc9f1ed36fca16b227f
generic

batman-adv: tt: fix TOCTOU race for reported vlans - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/211ea59988e1cba43cb0367ad65d379b56f9c3bd

Vendor Advisories for CVE-2026-64091(1)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

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 62× in last 7d / 366× 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 440 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64091?
CVE-2026-64091 is a critical vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: batman-adv: tt: fix TOCTOU race for reported vlans The local TT based TVLV is generated by first checking the number of VLANs which have at least one TT entry. A new buffer with the correct size for the VLANs is then allocated.…
When was CVE-2026-64091 disclosed?
CVE-2026-64091 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64091 actively exploited?
CVE-2026-64091 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 64.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64091?
CVE-2026-64091 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-64091?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64091, 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-64091

Explore →

Is Your Infrastructure Affected by CVE-2026-64091?

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

Start Free Scan →Browse All CVEs