CVE-2026-74474

vxlan: use pskb_network_may_pull() for transmit path header pulls

State
Published
Severity
9.8 Critical
Published
Aug 15, 2026
Updated
Oct 16, 2026
Reserved
Aug 15, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.19.8 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • e4f67addf158f98f8197e08974966b18480dc751 to before 371425d4be7795e9158388af9eee0201e6047410Affected
  • e4f67addf158f98f8197e08974966b18480dc751 to before bb01c51950c3ff3c76acdd54b85ab38ccc2a8bb4Affected
  • e4f67addf158f98f8197e08974966b18480dc751 to before 6146901881f09ef063eb34ad389f63231f8486f5Affected
  • e4f67addf158f98f8197e08974966b18480dc751 to before 94dee751aad627b3645d424b5d0c736d394573e9Affected
  • e4f67addf158f98f8197e08974966b18480dc751 to before 7076a34b6e33315dc160b4612bfea1c597495585Affected
  • e4f67addf158f98f8197e08974966b18480dc751 to before b9553558b48db54ac9273e6b98d7263ef5c1a329Affected
LinuxLinux
  • 3.8Affected
  • before 3.8Not affected
  • 6.1.188 through 6.1.*Not affected
  • 6.6.153 through 6.6.*Not affected
  • 6.12.105 through 6.12.*Not affected
  • 6.18.44 through 6.18.*Not affected
  • 7.1.8 through 7.1.*Not affected
  • 7.2 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.