CVE-2026-74474

CriticalCVSS 9.8

Published: 15/08/2026(UTC)Updated: 17/08/2026(UTC)Translated: 15/08/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.17%

6th percentile - higher than 6% of all known CVEs

Summary

In the Linux kernel, the vxlan module's vxlan_xmit(), arp_reduce(), and vxlan_mdb_entry_skb_get() functions use pskb_may_pull() instead of pskb_network_may_pull(), which does not account for the MAC header offset and can leave part of the network header in non-linear frags.

Risk Assessment

This can lead to incorrect packet processing and potentially to crashes or network misbehavior.

Recommendation

Apply the kernel patch that replaces these calls with pskb_network_may_pull() to properly account for the MAC header offset.

Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: vxlan: use pskb_network_may_pull() for transmit path header pulls In vxlan_xmit(), arp_reduce(), and vxlan_mdb_entry_skb_get(), pskb_may_pull() was being called to verify the availability of network layer headers (ARP, IPv6/ND, IP/IPv6 MDB keys). However, during transmit skb->data points to the MAC header, so skb_network_offset(skb) is ETH_HLEN (14 bytes). Using pskb_may_pull(skb, len) only checks len bytes from skb->data rather than skb_network_offset(skb) + len, which can leave part of the network header in non-linear frags. Replace these remaining pskb_may_pull() calls with pskb_network_may_pull() to properly account for the MAC header offset.