PT-2026-152646

CVE-2026-99767

·

Published

2026-11-20

·

Updated

2026-11-20

Description by

Score
N/A
Not available

No 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:
xfrm4: use a full socket for local errors
xfrm4 local error() passes skb->sk to inet sk() and ip local error() without ensuring it points to a full socket. TCP SYN-ACK skbs can be owned by TCP NEW SYN RECV request sockets.
xfrm4 tunnel check size() already checks sk fullsock() since commit 1620c88887b1 ("xfrm: Fix the usage of skb->sk"), so iptfs is too big() is the only remaining IPv4 caller passing a request socket here: the sk it tests is the listener, while skb->sk is the request socket.
When IP-TFS rejects such an skb because it exceeds its payload MTU, the local error path treats the request socket as a struct inet sock. KASAN reports a slab-out-of-bounds read in ip local error() beyond the request sock TCP allocation.
Resolve the skb owner with skb to full sk() before accessing inet sock state or reporting the error. This maps a request socket to its listener and rejects sockets that cannot be used as full sockets, matching what commit 6973a21ee73c ("ipv6: xfrm: use full sockets in local error paths") did for xfrm6 local error().
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾