Skip to main content

Linux Kernel EUVDEUVD-2026-45778

| CVE-2026-64093 HIGH
2026-07-19 Linux GHSA-qf88-xw8w-824g
8.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
8.8 HIGH
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
5.9 MEDIUM

Adjacent unauthenticated mesh peer (AV:A/PR:N) must win a narrow shutdown race (AC:H); the UAF most plausibly causes a kernel panic (A:H) with limited corruption (I:L) and no clear disclosure (C:N).

3.1 AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H
4.0 AV:A/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 20, 2026 - 17:23 vuln.today
CVSS changed
Jul 20, 2026 - 15:22 NVD
8.8 (HIGH)
Patch available
Jul 19, 2026 - 17:03 EUVD
CVE Published
Jul 19, 2026 - 15:40 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 19, 2026 - 15:40 cve.org
HIGH 8.8

DescriptionCVE.org

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:

  1. context 0 (batadv_tp_recv_ack()) checks in

batadv_tp_reset_sender_timer() if sending is still 1 -> it is

  1. 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()

  1. context 0 continues in batadv_tp_reset_sender_timer() and rearms the

timer -> but the reference for it is already gone

AnalysisAI

Use-after-free race condition in the Linux kernel's batman-adv (B.A.T.M.A.N. advanced) mesh-networking throughput meter (tp_meter) can corrupt kernel memory when a sender timer is re-armed after its backing reference has already been freed during cleanup. The flaw affects systems that load the batman-adv module and run tp_meter sessions; an adjacent mesh peer's ACK can race the shutdown path (batadv_tp_sender_shutdown) so that batadv_tp_reset_sender_timer() re-arms a timer whose object is gone. CVSS is rated 8.8 (AV:A), but with EPSS at 0.21% (11th percentile), no CISA KEV listing, and no public exploit identified at time of analysis, real-world exploitation risk is low.

Technical ContextAI

batman-adv is an in-kernel Layer-2 mesh routing protocol (net/batman-adv) that operates over adjacent broadcast domains. The affected component, tp_meter, is its built-in throughput-measurement facility, which uses kernel timers to retransmit and to reset sender state as ACKs arrive. The root cause is a timer-lifetime use-after-free race (CWE-416 combined with CWE-362, listed as N/A in the feed): batadv_tp_sender_cleanup() previously used timer_delete_sync() followed by timer_delete() as a hack to defeat a handler that could re-arm itself, relying on the sending status being cleared to 0 to suppress re-arming. Because that suppression was conditional, a concurrent batadv_tp_recv_ack() path in batadv_tp_reset_sender_timer() could observe sending==1, then re-arm the timer after batadv_tp_sender_shutdown() had already set sending to 0 and forced the kthread to tear the timer down - leaving a dangling timer reference. The fix replaces both calls with a single timer_shutdown_sync(), which waits for any running callback and permanently disarms the timer so it cannot be re-armed, making the guarantee unconditional. The two CPE entries only identify 'linux:linux' generically and do not pin the module.

RemediationAI

Vendor-released patch: upgrade to a fixed stable kernel - 5.15.210, 6.1.176, 6.6.143, 6.12.93, 6.18.34, 7.0.11, or mainline 7.1 (or later on your series). The corresponding stable commits are available at git.kernel.org/stable (e.g. https://git.kernel.org/stable/c/f86b20ec8d17d77bddc02c5c86cfa2389d84ecff and the sibling commits listed for CVE-2026-64093); distribution users should apply their vendor kernel update that references this CVE. Where immediate patching is not possible, the most effective compensating control is to avoid loading the vulnerable code: blacklist or unload the batman-adv module (add 'blacklist batman_adv' under /etc/modprobe.d and rmmod batman_adv) on hosts that do not use B.A.T.M.A.N. mesh networking - the side effect is that any mesh interface built on batman-adv will stop functioning, so this is only safe on systems that do not rely on it. If batman-adv must stay loaded, avoid running or exposing tp_meter throughput tests and restrict which peers can join the adjacent mesh segment to trusted L2 devices only, accepting that this narrows but does not eliminate the race window.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

EUVD-2026-45778 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy