Skip to content
Systems

CVE-2026-64093

8.8
High
EPSS 0.34%Patch availableJul 21, 2026

Linux batman-adv timer cleanup bug enables kernel RCE/privilege escalation

common questions

Is CVE-2026-64093 being exploited?

Not confirmed. CVE-2026-64093 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-64093?

CVE-2026-64093 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-64093?

Yes. A fix has been recorded for CVE-2026-64093. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-64093 affect?

CVE-2026-64093 affects Linux kernel (batman-adv module), Devices using batman-adv for mesh networking. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64093?

Install kernel updates or disable batman-adv; reboot if kernel updated

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (batman-adv module)Devices using batman-adv for mesh networking
impact

Timer re-arm race leads to use-after-free in batman-adv, enabling kernel-level code execution or privilege escalation via network-local mesh packets.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and < 00bf4bb9947b1190a8be8d9b6a1bcbfa3707785c
  • affected>= 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and < 74a76634055462833446684fd526d73c290ea43a
  • affected>= 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and < 5bc2d50fb66b46f86543d5153a188eb1486d0b6e
  • affected>= 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and < f86b20ec8d17d77bddc02c5c86cfa2389d84ecff
  • affected>= 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and < 770bf0a35f0620b526fd4193889d1e77084e4c43
  • affected>= 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and < 933880a8bc9b4042223a79255c0b1021cdc36991
  • affected>= 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and < d5487249a81ea658717614009c8f46acc5b7101a
  • affected4.8
vendor says fixed in< 4.8, >= 5.15.210 and <= 5.15.*, >= 6.1.176 and <= 6.1.*, >= 6.6.143 and <= 6.6.*, >= 6.12.93 and <= 6.12.*, >= 6.18.34 and <= 6.18.*, >= 7.0.11 and <= 7.0.*, >= 7.1 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free