In the Linux kernel, the following vulnerability has been resolved: bpf: Disallow bpf_skb_pull_data() for LWT_SEG6LOCAL An LWT_SEG6LOCA…
CVE-2026-98383 · GHSA-ph4x-4wh2-2qrm · EUVD-2026-95538 · published 9 Oct 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-98383?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: patch: 5.15.222
- Linux Linux: patch: 6.12.112
- Linux Linux: patch: 0
- Linux Linux: patch: 6.18.55
- Linux Linux: 004d4b274e2a1a895a0e5dc66158b90a7d463d44 <0f38472a2aa8704a6b514c0dfa9c32f3672b8f32
- Linux Linux: patch: 5.10.271
- Linux Linux: 004d4b274e2a1a895a0e5dc66158b90a7d463d44 <e4a62833adff6ef0fe7c0b90393204fe3c26b5c5
- Linux Linux: 004d4b274e2a1a895a0e5dc66158b90a7d463d44 <b9bb0e735460751b620156f800a4279a28573392
- Linux Linux: 004d4b274e2a1a895a0e5dc66158b90a7d463d44 <cae8674489f26edf7553fdd660599466cbb4c32f
- Linux Linux: patch: 6.1.189
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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().
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/0f38472a2aa8704a6b514c0dfa9c32f3672b8f32
- git.kernel.org/stable/c/cae8674489f26edf7553fdd660599466cbb4c32f
- git.kernel.org/stable/c/9f9e57b5a3a033f95f49ef9d541340cdbcb80abb
- git.kernel.org/stable/c/df0072be6fc373cb22f9ea854d458b04e32a03cf
- git.kernel.org/stable/c/b9bb0e735460751b620156f800a4279a28573392
- git.kernel.org/stable/c/37b18688cd18fd86d2f35c212df1611862a26cd5
- git.kernel.org/stable/c/fca71ead7a20290af1e2046983eeafae43d21af1
- git.kernel.org/stable/c/e4a62833adff6ef0fe7c0b90393204fe3c26b5c5
Merged from ENISA EUVD. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON