vxlan: re-fetch eth header after route_shortcircuit()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ae8840825605f36f98f247323edc150e761cb64e · < 1235e017aa11cf01e91b613c4c5ed6aa28934fff| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
vxlan: re-fetch eth header after route_shortcircuit()
Before route_shortcircuit(), the eth header pointer is cached from eth_hdr(skb).
Inside route_shortcircuit(), pskb_may_pull() can be called, which may reallocate skb->head.
In this case, returning to vxlan_xmit() leaves the cached eth pointer pointing to freed memory, leading to a use-after-free when dereferencing eth->h_dest.
Fix this by updating eth = eth_hdr(skb) after calling route_shortcircuit().
From the CVE record · Linux
In the Linux kernel’s VXLAN transmit path, a cached Ethernet header pointer can become stale if route_shortcircuit() reallocates packet memory, leading to a use-after-free. The input does not establish how an attacker could trigger it, or whether network access, authentication, or user interaction is required.
Anyone running the Linux kernel should check whether their version is affected; affected versions were not provided.