net: cap advertised IP tunnel headroom
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1a37e412a0225fcba5587f24c0dfc7636efc8b69 · < af0ee8f04bea22cdb331fa3509e17f81b48938ad| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: cap advertised IP tunnel headroom
IP tunnel devices derive their advertised needed_headroom from lower output devices. A stack of user-created devices can make the derived value larger than the 16-bit skb header offsets can represent. Once IP output reserves it, skb head expansion can wrap those offsets.
The runtime transmit path already caps a growing needed_headroom at 512. Apply the same cap when tunnel configuration publishes needed_headroom derived from a lower output device.
Capping the advertised value is safe: IP tunnel transmit still expands the skb when a packet needs more headroom. A nonsensical stacked configuration can therefore incur an extra reallocation, but it cannot publish an unbounded reservation to upper layers.
From the CVE record · Linux
IP tunnel devices can advertise more headroom than 16-bit packet-buffer header offsets can represent. A local attacker who can create a stack of devices may cause those offsets to wrap during packet-buffer expansion; the input does not specify authentication requirements or user interaction.
Engineers running Linux kernels with IP tunnel devices should check their deployments; affected versions are not specified.