PT-2026-152495
CVE-2026-99615
·
Published
2026-11-20
·
Updated
2026-11-20
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
l2tp: only return sessions of the given tunnel in l2tp session get()
Commit 5f77c18ea556 ("l2tp: use IDR for all session lookups") made
pppol2tp connect() and the netlink session commands find sessions with
l2tp session get(), passing the socket of the tunnel they name.
L2TPv3 session IDs are unique per network namespace, except that
sessions carried over UDP are only unique per UDP socket, the socket of
their tunnel. However, l2tp v3 session get() only checks the socket when
another session has the same session ID. Otherwise it returns the
session, whichever tunnel it belongs to. As of now, a session command
that names the wrong tunnel acts on a session of another tunnel, and a
PPPoL2TP socket for a second L2TPv3 tunnel fails with EEXIST, because it
finds session 0 of the first tunnel.
The issue can be reproduced with:
ip l2tp add tunnel tunnel id 3 peer tunnel id 3 encap udp
local 127.0.0.1 remote 127.0.0.1 udp sport 5003 udp dport 6003
ip l2tp add tunnel tunnel id 4 peer tunnel id 4 encap udp
local 127.0.0.1 remote 127.0.0.1 udp sport 5004 udp dport 6004
ip l2tp add session tunnel id 3 session id 7 peer session id 7
ip l2tp del session tunnel id 4 session id 7
ip l2tp show session
Before that commit, the delete fails with "No such device", and session
7 of tunnel 3 is still listed. After that commit, the delete succeeds,
and session 7 of tunnel 3 is gone.
This patch will make l2tp session get() return NULL when the L2TPv3
session it finds does not belong to the given socket. The receive path
calls l2tp v3 session get() directly and is not changed.
Found an issue in the description? Have something to add? Feel free to write us 👾