{"uuid": "f7e7bcf0-fc36-401b-b1b2-cffe8e5e7572", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22021", "type": "seen", "source": "https://t.me/cvedetector/23074", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22021 - Kubernetes Cilium Envoy IPv6 SNAT Socket Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22021 \nPublished : April 16, 2025, 11:15 a.m. | 14\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetfilter: socket: Lookup orig tuple for IPv6 SNAT  \n  \nnf_sk_lookup_slow_v4 does the conntrack lookup for IPv4 packets to  \nrestore the original 5-tuple in case of SNAT, to be able to find the  \nright socket (if any). Then socket_match() can correctly check whether  \nthe socket was transparent.  \n  \nHowever, the IPv6 counterpart (nf_sk_lookup_slow_v6) lacks this  \nconntrack lookup, making xt_socket fail to match on the socket when the  \npacket was SNATed. Add the same logic to nf_sk_lookup_slow_v6.  \n  \nIPv6 SNAT is used in Kubernetes clusters for pod-to-world packets, as  \npods' addresses are in the fd00::/8 ULA subnet and need to be replaced  \nwith the node's external address. Cilium leverages Envoy to enforce L7  \npolicies, and Envoy uses transparent sockets. Cilium inserts an iptables  \nprerouting rule that matches on `-m socket --transparent` and redirects  \nthe packets to localhost, but it fails to match SNATed IPv6 packets due  \nto that missing conntrack lookup. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T13:31:24.000000Z"}