Skip to content
Networks

CVE-2026-46212

8.8
High
EPSS 0.27%Patch availableMay 30, 2026

Linux batman-adv use-after-free in claim cleanup.

common questions

Is CVE-2026-46212 being exploited?

Not confirmed. CVE-2026-46212 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.27% probability of exploitation in the next 30 days.

How severe is CVE-2026-46212?

CVE-2026-46212 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-46212?

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

What does CVE-2026-46212 affect?

CVE-2026-46212 affects Linux kernel (batman-adv). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-46212?

Update kernel to patched version

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)
impact

Kernel crash/memory corruption via batman-adv claim cleanup; potential DoS and possible escalation if exploited.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 23721387c409087fd3b97e274f34d3ddc0970b74 and < 1d4b241482d9025c537afb3c7c8419c72c0e0c82
  • affected>= 23721387c409087fd3b97e274f34d3ddc0970b74 and < a1a99837bb6169cfb9187abaa2005e8f12079426
  • affected>= 23721387c409087fd3b97e274f34d3ddc0970b74 and < b88c865dcf6e9f20bfe66a360d4b62941ef769b8
  • affected>= 23721387c409087fd3b97e274f34d3ddc0970b74 and < 368449e467d5f1e2c2e987bf2bd57000ba75e10b
  • affected>= 23721387c409087fd3b97e274f34d3ddc0970b74 and < 6c5dc6d68e6ba7f0224a757a39ed52fcdb54d472
  • affected>= 23721387c409087fd3b97e274f34d3ddc0970b74 and < 00155f336a5e8b1006d2ca9ae7ad8fc4a44bb401
  • affected>= 23721387c409087fd3b97e274f34d3ddc0970b74 and < 0cc9847c64cb6e61118bc78c9187c8209a7197fa
  • affected>= 23721387c409087fd3b97e274f34d3ddc0970b74 and < 4ae1709a314060a196981b344610d023ea841e57
  • affected3.5
vendor says fixed in< 3.5, >= 5.10.258 and <= 5.10.*, >= 5.15.209 and <= 5.15.*, >= 6.1.175 and <= 6.1.*, >= 6.6.140 and <= 6.6.*, >= 6.12.90 and <= 6.12.*, >= 6.18.32 and <= 6.18.*, >= 7.0.9 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