In the Linux kernel, the following vulnerability has been resolved: pfcp: make sure the SEID is linear before reading it pfcp_encap_rec…
CVE-2026-98952 · GHSA-cvm8-2x36-72mp · EUVD-2026-108926 · published 23 Oct 2026
How serious is it
- Severity: high, CVSS score 7.3 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-98952?
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: 0
- Linux Linux: 6dd514f48110ebb4bf36875b9e7e02d07b589caa <3192a5e398c64d48aad64a09e29643e327369bc4
- Linux Linux: patch: 6.18.57
- Linux Linux: 6dd514f48110ebb4bf36875b9e7e02d07b589caa <23609bce9e1de525d1d0e73fc68c6e7971d0b49e
- Linux Linux: 6dd514f48110ebb4bf36875b9e7e02d07b589caa <b18a6496495495e2dc27e525aa3315a0c59b9513
- Linux Linux: patch: 7.2.11
- Linux Linux: 6dd514f48110ebb4bf36875b9e7e02d07b589caa <2fb6d05f706d79bbdc88835be2f4f45ab56dd819
- Linux Linux: patch: 6.12.113
- Linux Linux: 6.10
- Linux Linux: patch: 7.3
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:
pfcp: make sure the SEID is linear before reading it
pfcp_encap_recv() only makes sure that the UDP header and the 4 byte
PFCP header are in the linear area. When the S flag is set,
pfcp_session_recv() then reads the 8 byte SEID that follows, which is
not covered by the pskb_may_pull() check.
A short PFCP packet with the S flag set, or one whose session header
lies in a fragment, therefore makes pfcp_session_recv() read beyond the
end of the packet data, and whatever it finds there is stored in the
tunnel metadata that flower later classifies on.
Pull up to the end of the SEID before reading it, and drop packets
that are too short to contain it. Reload the header pointer afterwards
since pskb_may_pull() may reallocate the skb head.
Use offsetofend() rather than sizeof(struct pfcphdr_session): the
structure is not packed, so its size is 16 bytes because of the
alignment of the __be64 member, while the header on the wire is only 12
bytes, and valid session messages would be dropped.
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/3192a5e398c64d48aad64a09e29643e327369bc4
- git.kernel.org/stable/c/b18a6496495495e2dc27e525aa3315a0c59b9513
- git.kernel.org/stable/c/2fb6d05f706d79bbdc88835be2f4f45ab56dd819
- git.kernel.org/stable/c/23609bce9e1de525d1d0e73fc68c6e7971d0b49e
- nvd.nist.gov/vuln/detail/CVE-2026-98952
Merged from ENISA EUVD. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON