CVE-2026-98383
bpf: Disallow bpf_skb_pull_data() for LWT_SEG6LOCAL
No known exploitation. EPSS puts it in the 5th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 004d4b274e2a1a895a0e5dc66158b90a7d463d44, < 0f38472a2aa8704a6b514c0dfa9c32f3672b8f32Upgrade to: 0f38472a2aa8704a6b514c0dfa9c32f3672b8f32Affected: ≥ 004d4b274e2a1a895a0e5dc66158b90a7d463d44, < cae8674489f26edf7553fdd660599466cbb4c32fUpgrade to: cae8674489f26edf7553fdd660599466cbb4c32fAffected: ≥ 004d4b274e2a1a895a0e5dc66158b90a7d463d44, < 9f9e57b5a3a033f95f49ef9d541340cdbcb80abbUpgrade to: 9f9e57b5a3a033f95f49ef9d541340cdbcb80abbAffected: ≥ 004d4b274e2a1a895a0e5dc66158b90a7d463d44, < df0072be6fc373cb22f9ea854d458b04e32a03cfUpgrade to: df0072be6fc373cb22f9ea854d458b04e32a03cf + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: bpf: Disallow bpf_skb_pull_data() for LWT_SEG6LOCAL An LWT_SEG6LOCAL program can invalidate its cached SRH with bpf_lwt_seg6_adjust_srh() and then call bpf_skb_pull_data(). The latter may reallocate skb->head, leaving the per-CPU SRH pointer dangling. Post-program SRH validation then writes through that pointer. Disallow bpf_skb_pull_data() for LWT_SEG6LOCAL programs so the verifier rejects this unsafe helper combination. Other LWT program types continue to expose the helper through lwt_out_func_proto().
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 5th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/0f38472a2aa8704a6b514c0dfa9c32f3672b8f32
- git.kernel.org/stable/c/cae8674489f26edf7553fdd660599466cbb4c32f
- git.kernel.org/stable/c/9f9e57b5a3a033f95f49ef9d541340cdbcb80abb
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI