CVE-2026-99762 in Linuxinfo

Summary

by MITRE • 11/20/2026

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

batman-adv: mcast: validate tracker padding before forwarding

A multicast tracker with an even number of destinations needs two padding bytes after its destination list. batadv_mcast_forw_packet() currently only checks that the count field and the addresses fit in the tracker TVLV.

If an unpadded even tracker is compacted to an odd number of destinations, batadv_mcast_forw_shrink_update_headers() includes those missing padding bytes in the amount to remove. The subsequent memmove can then write two bytes past the old packet tail. With no tailroom, this corrupts skb_shared_info.

Include the required padding in the existing tracker length check. This rejects the malformed tracker before either received or locally generated packets can reach the compactor.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/20/2026

The Linux kernel vulnerability identified within the batman-adv multicast tracking subsystem represents a critical memory corruption issue arising from improper validation of packet structure during optimization routines. The specific flaw resides in the handling of multicast trackers, which are data structures used to manage group membership and forwarding decisions for multicast traffic. According to protocol specifications, when a multicast tracker contains an even number of destination addresses, it is required to append two padding bytes after the list of destinations to maintain proper alignment and structure integrity. The original implementation failed to enforce this structural requirement strictly enough during initial validation phases, allowing malformed packets with missing padding to enter the processing pipeline.

The operational impact manifests when a multicast tracker possessing an even number of destinations undergoes compaction or shrinking operations via the batadv_mcast_forw_shrink_update_headers function. During this process, the system attempts to optimize packet headers by removing unnecessary data. However, because the initial validation did not account for the mandatory padding bytes associated with even-count trackers, the shrink logic incorrectly calculates the amount of data to remove. It assumes that all trailing bytes are part of the destination list and proceeds to trim them. This miscalculation leads to a subsequent memory move operation, memmove, which writes two bytes past the end of the old packet tail buffer.

This out-of-bounds write results in severe corruption of kernel memory structures, specifically targeting the skb_shared_info structure associated with the socket buffer. The skb_shared_info is a critical data structure that holds metadata about network packets, including reference counts and fragment information. Corruption of this area can lead to unpredictable system behavior, potential denial of service conditions due to kernel panics or crashes, and in more complex scenarios, could potentially be exploited for arbitrary code execution if an attacker can control the contents written into these corrupted memory regions. The vulnerability is particularly dangerous because it affects both received packets from external sources and locally generated traffic processed by the batman-adv module.

From a classification perspective, this flaw aligns with CWE-120 Buffer Copy without Checking Size of Input, as the code performs a copy operation that exceeds the bounds of the allocated buffer due to incorrect size calculations derived from insufficient input validation. Furthermore, it relates to CWE-20 Improper Input Validation, since the system failed to verify that the packet structure adhered to the required padding constraints before proceeding with memory manipulation operations. In terms of attack vectors and techniques, this vulnerability could be leveraged within an ATT&CK framework context under T1498 Network Denial of Service or potentially as a precursor for privilege escalation if the kernel crash can be manipulated to leak information or execute code in ring zero.

To mitigate this risk, the resolution involves updating the tracker length check logic to explicitly include the required padding bytes when validating even-numbered destination lists. By rejecting malformed trackers that lack these mandatory two-byte paddings before they reach the compactor functions like batadv_mcast_forw_shrink_update_headers, the system prevents the erroneous memory calculations and subsequent out-of-bounds writes. This fix ensures that only structurally valid packets are processed for optimization, thereby preserving the integrity of kernel memory structures such as skb_shared_info. System administrators should apply the relevant kernel updates or patches provided by their distribution vendors to address this issue in batman-adv implementations immediately.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00168

KEV

no

Activities

low

Sources

Do you need the next level of professionalism?

Upgrade your account now!