CVE-2026-99767: xfrm4: use a full socket for local errors
In the Linux kernel, the following vulnerability has been resolved:
xfrm4: use a full socket for local errors
xfrm4localerror() passes skb->sk to inetsk() and iplocalerror() without ensuring it points to a full socket. TCP SYN-ACK skbs can be owned by TCPNEWSYNRECV request sockets.
xfrm4tunnelchecksize() already checks skfullsock() since commit 1620c88887b1 ("xfrm: Fix the usage of skb->sk"), so iptfsistoobig() 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 inetsock. KASAN reports a slab-out-of-bounds read in iplocalerror() beyond the requestsockTCP allocation.
Resolve the skb owner with skbtofullsk() before accessing inetsock 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 xfrm6localerror().
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.5-1
Event History
Frequently Asked Questions
What traffic path is required to trigger the vulnerable error handling?
The issue is reached when IP-TFS rejects an IPv4 TCP SYN-ACK skb because it exceeds the configured IP-TFS payload MTU. The affected skb can be owned by a TCP_NEW_SYN_RECV request socket rather than a full socket.
What is the observable impact if the condition is triggered?
The local-error path can treat a TCP request socket as a struct inet_sock and read beyond the request_sock_TCP allocation. KASAN reports this as a slab-out-of-bounds read in ip_local_error().
What should be done if the update cannot be applied immediately?
The provided information identifies the triggering condition as IP-TFS rejecting oversized TCP SYN-ACK traffic. No specific workaround or configuration mitigation is provided.
How can I determine whether a system has encountered this issue?
A KASAN-enabled kernel may report a slab-out-of-bounds read in ip_local_error() when the condition occurs. The relevant path involves IP-TFS payload-MTU rejection of a TCP SYN-ACK associated with a TCP_NEW_SYN_RECV request socket.