ipvlan: inherit needed_headroom and needed_tailroom from phy_dev
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2ad7bf3638411cb547f2823df08166c13ab04269 · < e16e960d55a40d36bd7c2494cc005e757dc9a1ef| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ipvlan: inherit needed_headroom and needed_tailroom from phy_dev
ipvlan devices inherit hard_header_len from phy_dev during ipvlan_init(), but leave needed_headroom and needed_tailroom set to 0.
When the underlying phy_dev (or stacked lower device) requires extra headroom or tailroom for headers/trailers (e.g. macsec, ipsec, wireguard, tunnels, or veth with rx headroom), upper layers calculating packet headroom and tailroom fail to reserve sufficient space.
This can result in reallocation overhead, skb headroom underflows, or KASAN slab-use-after-free crashes when dev_hard_header() / ipvlan_hard_header() prepends header data or when lower devices append tailroom.
Fix this by: 1. Inheriting needed_headroom and needed_tailroom from phy_dev in ipvlan_init(). 2. Propagating needed_headroom and needed_tailroom updates to attached ipvlans in ipvlan_device_event() when receiving NETDEV_FEAT_CHANGE events.
From the CVE record · Linux
Linux ipvlan devices can fail to reserve required packet headroom or tailroom when an underlying device needs extra space for headers or trailers. This can cause packet reallocation overhead, headroom underflows, or KASAN slab-use-after-free crashes. The input does not establish how an attacker could trigger this, whether authentication is needed, or whether user interaction is required.
Engineers running Linux kernels with ipvlan devices should check their versions; affected versions were not provided.