CVE-2026-89951

HIGHCVSS 8.8/10EPSS 0.34%

Last modified

CVE-2026-89951 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: batman-adv: fix stale receive device on merged fragments Fragment reassembly reuses the skb from the highest-numbered buffered fragment as the merged packet. When that fragment was received on a hard interface which is deleted before the chain completes, the merged skb can re-enter the receive path with a stale skb->dev and skb_iif. batadv_batman_skb_recv() passes such merged packets through the normal receive handlers again. EPSS estimates a 0.34% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: batman-adv: fix stale receive device on merged fragments Fragment reassembly reuses the skb from the highest-numbered buffered fragment as the merged packet. When that fragment was received on a hard interface which is deleted before the chain completes, the merged skb can re-enter the receive path with a stale skb->dev and skb_iif. batadv_batman_skb_recv() passes such merged packets through the normal receive handlers again. DAT and bridge loop avoidance both derive the ARP header length from skb->dev, so they can dereference the freed net_device before the packet reaches the local mesh interface. Refresh the receive device metadata from the current receive device before running the packet handlers. This keeps internally reinjected merged fragments consistent with the normal receive path after hard interface teardown.

Metrics

EPSS Probability
0.34%

26.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 610bfc6bc99bc83680d190ebc69359a05fc7f605, < 63d86250fa7cbe22451369bd1c0881dfc8190958; >= 610bfc6bc99bc83680d190ebc69359a05fc7f605, < f830c2dfc1431764db9256b3d5db1695fc9a7f56; >= 610bfc6bc99bc83680d190ebc69359a05fc7f605, < f4b4ae763b5d59319fad62a00c76676758e7dafa; >= 610bfc6bc99bc83680d190ebc69359a05fc7f605, < 6df64825f8b199921120c685af2abca14b077331; >= 610bfc6bc99bc83680d190ebc69359a05fc7f605, < a2c272da99c2077088083c14961cf2f1e4506995; >= 610bfc6bc99bc83680d190ebc69359a05fc7f605, < e91d2cc7441d89a45bad73ad9789159c7441cb80; >= 610bfc6bc99bc83680d190ebc69359a05fc7f605, < 2dffc8c44b6e3347b3719c6419c07b4a18fea895; >= 610bfc6bc99bc83680d190ebc69359a05fc7f605, < ad46c907d7d9975a285c1e89a4adde652eaa93f5
LinuxLinux3.13

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-89951?
In the Linux kernel, the following vulnerability has been resolved: batman-adv: fix stale receive device on merged fragments Fragment reassembly reuses the skb from the highest-numbered buffered fragment as the merged packet. When that fragment was received on a hard interface which is deleted before the chain completes, the merged skb can re-enter the receive path with a stale skb->dev and skb_iif. batadv_batman_skb_recv() passes such merged packets through the normal receive handlers again. DAT and bridge loop avoidance both derive the ARP header length from skb->dev, so they can dereference the freed net_device before the packet reaches the local mesh interface. Refresh the receive device metadata from the current receive device before running the packet handlers. This keeps internally reinjected merged fragments consistent with the normal receive path after hard interface teardown.
How severe is CVE-2026-89951?
CVE-2026-89951 has a CVSS score of 8.8/10 (HIGH severity). The EPSS model estimates a 0.34% probability of exploitation in the next 30 days.
How do I fix CVE-2026-89951?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-89951?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST