CVE-2026-64093

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

batman-adv: tp_meter: directly shut down timer on cleanup

batadv_tp_sender_cleanup() was calling timer_delete_sync() followed by timer_delete() to guard against the timer handler re-arming itself between the two calls. This double-deletion hack relied on the sending status being set to 0 to suppress re-arming.

Replace both calls with a single timer_shutdown_sync(). This function both waits for any running timer callback to complete (like timer_delete_sync()) and permanently disarms the timer so it cannot be re-armed afterwards, making re-arming prevention unconditional and self-documenting.

The re-arming property is also required because otherwise:

  • context 0 (batadv_tp_recv_ack()) checks in
batadv_tp_reset_sender_timer() if sending is still 1 -> it is
  • context 1 changes in batadv_tp_sender_shutdown() sending to 0 and in
this process forces the kthread to stop timer in batadv_tp_sender_cleanup()
  • context 0 continues in batadv_tp_reset_sender_timer() and rearms the
timer -> but the reference for it is already gone

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

Published

July 19, 2026

Last Modified

August 11, 2026

Advisory Details (7)

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

batman-adv: tp_meter: directly shut down timer on cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: tp_meter: directly shut down timer on cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: tp_meter: directly shut down timer on cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/933880a8bc9b4042223a79255c0b1021cdc36991
generic

batman-adv: tp_meter: directly shut down timer on cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/770bf0a35f0620b526fd4193889d1e77084e4c43
generic

batman-adv: tp_meter: directly shut down timer on cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/74a76634055462833446684fd526d73c290ea43a
generic

batman-adv: tp_meter: directly shut down timer on cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5bc2d50fb66b46f86543d5153a188eb1486d0b6e
generic

batman-adv: tp_meter: directly shut down timer on cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/00bf4bb9947b1190a8be8d9b6a1bcbfa3707785c

Vendor Advisories for CVE-2026-64093(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-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
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

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 ... 7.2~rc5-1~exp1 (496 versions)——
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—

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 32× in last 7d / 161× 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 211 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64093?
CVE-2026-64093 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: batman-adv: tp_meter: directly shut down timer on cleanup batadvtpsendercleanup() was calling timerdelete_sync() followed by timer_delete() to guard against the timer handler re-arming itself between the two calls. This…
When was CVE-2026-64093 disclosed?
CVE-2026-64093 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-64093 actively exploited?
CVE-2026-64093 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 73.7% of all scored CVEs.
What is the CVSS score of CVE-2026-64093?
CVE-2026-64093 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-64093?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64093, 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-64093

Explore →

Is Your Infrastructure Affected by CVE-2026-64093?

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

Start Free Scan →Browse All CVEs