CVE-2026-90160

lwt_bpf: Restore reserved headroom after xmit program

N/A
Published: September 17, 2026 at 04:06 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: lwt_bpf: Restore reserved headroom after xmit program ip_finish_output2() expands an skb to LL_RESERVED_SPACE(dev) before LWT xmit. An LWT_XMIT BPF program can then modify the skb head and still return BPF_OK, so bpf_xmit() rechecks the remaining headroom before the skb continues to neighbour output. That recheck uses dst->dev->hard_header_len. This is not enough for the neighbour cached-header path: neigh_hh_output() copies the cached hardware header using the aligned hh_cache size, HH_DATA_MOD for short headers or HH_DATA_ALIGN(hh_len) otherwise. On Ethernet, hard_header_len is 14 but the cached copy needs 16 bytes. If an LWT_XMIT BPF program calls bpf_skb_change_head(skb, 1, 0), the skb can still have 15 bytes of headroom after the program. The existing check accepts that, after which neigh_hh_output() hits its headroom warning and drops the skb. Use LL_RESERVED_SPACE(dst->dev) in the post-BPF headroom check to match the reservation made before LWT xmit.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3a0af8fd61f90920f6fa04e4f1e9a6a73c1b4fd24.10
Vendor states this is fixed in 179a5b2171573d94a25c9aa8e1c9f9ac352ad316 (fixed)
Vendor states this is fixed in 5fe7007aed9ad069b2bd77e5d0c875c64f5c0269 (fixed)
Vendor states this is fixed in 753e5cdcca5474d230d62bb3489e5168ab27c272 (fixed)
Vendor states this is fixed in 7cf561843ed0ad57501892a65abb77957e6c800f (fixed)
Vendor states this is fixed in 7d043e24520a273c362be5dd7d9c82796879a49b (fixed)
Vendor states this is fixed in a38c0eb447e2dd0120a2ebcdba470f9505ac8907 (fixed)
Vendor states this is fixed in c488071c3441fa34f5a87cd6c12ce2cc6304f20e (fixed)
Vendor states this is fixed in de2b2004e16f2930eb689175e2c1998b0a68d499 (fixed)
Vendor states this is fixed in 4.10 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card