ipv6: xfrm: use full sockets in local error paths
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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().
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From dd767856a36e00b631d65ebc4bb81b19915532d6 · fixed in b1a88633c36d2cbc3831382f3846754d344276fd; From dd767856a36e00b631d65ebc4bb81b19915532d6 · fixed in 904a0e827d0d7189271a3a2eb648293809f25efc; From dd767856a36e00b631d65ebc4bb81b19915532d6 · fixed in 675919e08ce266b8cac11fd9af29170e762a480f; From dd767856a36e00b631d65ebc4bb81b19915532d6 · fixed in 60459c670329d586a58db5d8f811fa5accfe4862; From dd767856a36e00b631d65ebc4bb81b19915532d6 · fixed in ca3d68c3213475b53db6647e159dc73bd1af5ab1; From dd767856a36e00b631d65ebc4bb81b19915532d6 · fixed in 4c030a0400ebfd2318361c923a88103b2c67c49f; From dd767856a36e00b631d65ebc4bb81b19915532d6 · fixed in c21f3f7fbfeda7c5794f606cb0ffcc2d9001eef8; From dd767856a36e00b631d65ebc4bb81b19915532d6 · fixed in 6973a21ee73c5567f883813c8ef414774b45892f
- Linux Linux
3.2
- KernelLinux
From 3.2.0 · fixed in 5.10.271; From 5.11.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.54; From 6.19.0 · fixed in 7.2.8
References 8
git.kernel.org
- stable/c/b1a88633c36d2cbc3831382f3846754d344276fd
- stable/c/904a0e827d0d7189271a3a2eb648293809f25efc
- stable/c/675919e08ce266b8cac11fd9af29170e762a480f
- stable/c/60459c670329d586a58db5d8f811fa5accfe4862
- stable/c/ca3d68c3213475b53db6647e159dc73bd1af5ab1
- stable/c/4c030a0400ebfd2318361c923a88103b2c67c49f
- stable/c/c21f3f7fbfeda7c5794f606cb0ffcc2d9001eef8
- stable/c/6973a21ee73c5567f883813c8ef414774b45892f