CVE-2026-99767: xfrm4: use a full socket for local errors

Published Nov 20, 2026
·
Updated

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

4 affected componentsFixes available
linux/kernel>=6.14.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux<=7.3.4-1
6.1.176-16.1.192-26.12.107-16.12.117-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  3. Upgrade

    Upgrade debian/linux to 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

Nov 20, 2026
CVE Published
via MITRE·05:51 AM
Data Sourced
via MITRE·05:51 AM
Description
Data Sourced
via OSV·05:51 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

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.

2

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().

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203