vxlan: use pskb_network_may_pull() for transmit path header pulls
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e4f67addf158f98f8197e08974966b18480dc751 · < b9553558b48db54ac9273e6b98d7263ef5c1a329| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s VXLAN transmit path can check too few bytes when verifying ARP, IPv6/ND, and multicast database network headers, leaving part of a header in non-linear fragments. The input does not specify what an attacker could do, how the issue could be reached, whether authentication is needed, or whether user interaction is required.
Engineers running Linux kernels with VXLAN should check their versions against the vendor advisory; affected versions are not specified.