net: cap advertised IP tunnel headroom
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 1a37e412a0225fcba5587f24c0dfc7636efc8b69 · fixed in fb889a619723032140f5d983a3a34d25a5a2bed4; From 1a37e412a0225fcba5587f24c0dfc7636efc8b69 · fixed in b160422f8103574425e2834130e169d84c94fa1d; From 1a37e412a0225fcba5587f24c0dfc7636efc8b69 · fixed in d36e75f5669140b66515ad3a176ca6337bd80a5e; From 1a37e412a0225fcba5587f24c0dfc7636efc8b69 · fixed in 84783961cb8bdb36b4f41a02ce43aafc6d52b176; From 1a37e412a0225fcba5587f24c0dfc7636efc8b69 · fixed in bc4e05ae66c9797a0972ac44326e69c5305e0020; From 1a37e412a0225fcba5587f24c0dfc7636efc8b69 · fixed in af0ee8f04bea22cdb331fa3509e17f81b48938ad; From 1a37e412a0225fcba5587f24c0dfc7636efc8b69 · fixed in 9144f2c53a04465a6878172b523f640313c5559e; From 1a37e412a0225fcba5587f24c0dfc7636efc8b69 · fixed in 6b222adeb9340306e2ff97127c76117abb9b3df8
- Linux Linux
3.11
- KernelLinux
From 3.11.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4
References 8
git.kernel.org
- stable/c/fb889a619723032140f5d983a3a34d25a5a2bed4
- stable/c/b160422f8103574425e2834130e169d84c94fa1d
- stable/c/d36e75f5669140b66515ad3a176ca6337bd80a5e
- stable/c/84783961cb8bdb36b4f41a02ce43aafc6d52b176
- stable/c/bc4e05ae66c9797a0972ac44326e69c5305e0020
- stable/c/af0ee8f04bea22cdb331fa3509e17f81b48938ad
- stable/c/9144f2c53a04465a6878172b523f640313c5559e
- stable/c/6b222adeb9340306e2ff97127c76117abb9b3df8