CVE-2026-98952

High

Description

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.

SeverityHigh
CVSS7.3
Exploit probability—
ProductLinux
PublishedOct 23, 2026
First seenOct 23, 2026

How to fix

Update
  • Linux Linux3192a5e398c64d48aad64a09e29643e327369bc4, b18a6496495495e2dc27e525aa3315a0c59b9513, 2fb6d05f706d79bbdc88835be2f4f45ab56dd819, 23609bce9e1de525d1d0e73fc68c6e7971d0b49e or later

Affected products

ProductAffected versionsFixed in
Linux Linux6dd514f48110ebb4bf36875b9e7e02d07b589caa ≤ v < 3192a5e398c64d48aad64a09e29643e327369bc4, 6dd514f48110ebb4bf36875b9e7e02d07b589caa ≤ v < b18a6496495495e2dc27e525aa3315a0c59b9513, 6dd514f48110ebb4bf36875b9e7e02d07b589caa ≤ v < 2fb6d05f706d79bbdc88835be2f4f45ab56dd819, 6dd514f48110ebb4bf36875b9e7e02d07b589caa ≤ v < 23609bce9e1de525d1d0e73fc68c6e7971d0b49e, 6.103192a5e398c64d48aad64a09e29643e327369bc4, b18a6496495495e2dc27e525aa3315a0c59b9513, 2fb6d05f706d79bbdc88835be2f4f45ab56dd819, 23609bce9e1de525d1d0e73fc68c6e7971d0b49e

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.