From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98952: pfcp: make sure the SEID is linear before reading it
Date: Fri, 23 Oct 2026 14:19:14 +0200 [thread overview]
Message-ID: <2026102306-CVE-2026-98952-69a3@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-98952 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.10 with commit 6dd514f48110ebb4bf36875b9e7e02d07b589caa and fixed in 6.12.113 with commit 3192a5e398c64d48aad64a09e29643e327369bc4
Issue introduced in 6.10 with commit 6dd514f48110ebb4bf36875b9e7e02d07b589caa and fixed in 6.18.57 with commit b18a6496495495e2dc27e525aa3315a0c59b9513
Issue introduced in 6.10 with commit 6dd514f48110ebb4bf36875b9e7e02d07b589caa and fixed in 7.2.11 with commit 2fb6d05f706d79bbdc88835be2f4f45ab56dd819
Issue introduced in 6.10 with commit 6dd514f48110ebb4bf36875b9e7e02d07b589caa and fixed in 7.3 with commit 23609bce9e1de525d1d0e73fc68c6e7971d0b49e
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-98952
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/net/pfcp.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/3192a5e398c64d48aad64a09e29643e327369bc4
https://git.kernel.org/stable/c/b18a6496495495e2dc27e525aa3315a0c59b9513
https://git.kernel.org/stable/c/2fb6d05f706d79bbdc88835be2f4f45ab56dd819
https://git.kernel.org/stable/c/23609bce9e1de525d1d0e73fc68c6e7971d0b49e
reply other threads:[~2026-10-23 12:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026102306-CVE-2026-98952-69a3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.