CVE Catalog

CVE-2026-98241

HighCVSS 7.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.14%

3th percentile - higher than 3% of all known CVEs

Summary

In the Linux kernel IPv6 XFRM, xfrm6_local_rxpmtu() and xfrm6_local_error() assume skb->sk always points to a full IPv6 socket, but it can be a request_sock, leading to out-of-bounds reads. The fix uses skb_to_full_sk() and bails out when no full socket is attached.

Risk Assessment

The vulnerability may lead to memory disclosure or system crashes during processing of packets with lower MTU on XFRM routes.

Recommendation

Apply a Linux kernel update containing the fix for IPv6 XFRM full socket handling.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: ipv6: xfrm: use full sockets in local error paths xfrm6_local_rxpmtu() and xfrm6_local_error() dereference skb->sk as if it always pointed at a full IPv6 socket. That is not guaranteed. TCP SYN-ACK skbs can be owned by a TCP_NEW_SYN_RECV request_sock while the output path itself is driven by the full listener. If rerouting selects an IPv6 XFRM tunnel route with a lower MTU, the local PMTU/error handling path can reach these callbacks with that mini-socket still attached to the skb. The callbacks then miscast the request socket as a full inet/IPv6 socket and can read beyond the request_sock allocation when they access inet_sock or ipv6_pinfo state. Resolve the owner with skb_to_full_sk() in both callbacks and bail out when no full socket is attached. This matches the surrounding XFRM IPv6 PMTU/error logic, which already reasons about full sockets with skb_to_full_sk().

Vulnerability data from NVD (NIST) · CISA KEV · EPSS