CVE-2026-90160: lwt_bpf: Restore reserved headroom after xmit program
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 179a5b2171573d94a25c9aa8e1c9f9ac352ad316, 5fe7007aed9ad069b2bd77e5d0c875c64f5c0269, 753e5cdcca5474d230d62bb3489e5168ab27c272.
Low priority for now. Upgrade to Linux Linux 179a5b2171573d94a25c9aa8e1c9f9ac352ad316, 5fe7007aed9ad069b2bd77e5d0c875c64f5c0269, 753e5cdcca5474d230d62bb3489e5168ab27c272 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.10affected
- 3a0af8fd61f90920f6fa04e4f1e9a6a73c1b4fd2 and later · before 753e5cdcca5474d230d62bb3489e5168ab27c272affected · git
- 3a0af8fd61f90920f6fa04e4f1e9a6a73c1b4fd2 and later · before c488071c3441fa34f5a87cd6c12ce2cc6304f20eaffected · git
- 3a0af8fd61f90920f6fa04e4f1e9a6a73c1b4fd2 and later · before a38c0eb447e2dd0120a2ebcdba470f9505ac8907affected · git
- 3a0af8fd61f90920f6fa04e4f1e9a6a73c1b4fd2 and later · before de2b2004e16f2930eb689175e2c1998b0a68d499affected · git
- 3a0af8fd61f90920f6fa04e4f1e9a6a73c1b4fd2 and later · before 7d043e24520a273c362be5dd7d9c82796879a49baffected · git
- 3a0af8fd61f90920f6fa04e4f1e9a6a73c1b4fd2 and later · before 7cf561843ed0ad57501892a65abb77957e6c800faffected · git
- 3a0af8fd61f90920f6fa04e4f1e9a6a73c1b4fd2 and later · before 179a5b2171573d94a25c9aa8e1c9f9ac352ad316affected · git
- 3a0af8fd61f90920f6fa04e4f1e9a6a73c1b4fd2 and later · before 5fe7007aed9ad069b2bd77e5d0c875c64f5c0269affected · git
- before 4.10not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90158Sep 17, 2026 · m68k: nfcon: Do not call console_is_registered() in nfcon_device()0Monitor
- ← EarlierCVE-2026-90159Sep 17, 2026 · bpf: Disallow bpf_{g,s}etsockopt() in cgroup UNIX getname hooks0Monitor
- Later →CVE-2026-90161Sep 17, 2026 · erofs: fix interlaced ztailpacking pclusters28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 179a5b2171573d94a25c9aa8e1c9f9ac352ad316 | Vendor (CNA) |
| Linux Linux | 5fe7007aed9ad069b2bd77e5d0c875c64f5c0269 | Vendor (CNA) |
| Linux Linux | 753e5cdcca5474d230d62bb3489e5168ab27c272 | Vendor (CNA) |
| Linux Linux | 7cf561843ed0ad57501892a65abb77957e6c800f | Vendor (CNA) |
| Linux Linux | 7d043e24520a273c362be5dd7d9c82796879a49b | Vendor (CNA) |
| Linux Linux | a38c0eb447e2dd0120a2ebcdba470f9505ac8907 | Vendor (CNA) |
| Linux Linux | c488071c3441fa34f5a87cd6c12ce2cc6304f20e | Vendor (CNA) |
| Linux Linux | de2b2004e16f2930eb689175e2c1998b0a68d499 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/5fe7007aed9ad069b2bd77e5d0c875c64f5c0269
- git.kernel.org/stable/c/753e5cdcca5474d230d62bb3489e5168ab27c272
- git.kernel.org/stable/c/7cf561843ed0ad57501892a65abb77957e6c800f
- git.kernel.org/stable/c/7d043e24520a273c362be5dd7d9c82796879a49b
- git.kernel.org/stable/c/a38c0eb447e2dd0120a2ebcdba470f9505ac8907
- git.kernel.org/stable/c/c488071c3441fa34f5a87cd6c12ce2cc6304f20e
- git.kernel.org/stable/c/de2b2004e16f2930eb689175e2c1998b0a68d499
Vendor advisories and official records. Exploit/PoC links are deliberately left out.