CVE-2025-22021 in the critical feed json
netfilter: socket: Lookup orig tuple for IPv6 SNAT
published last yr. modified 25d ago also EUVD-2025-11372
- cvss
- 10.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
netfilter: socket: Lookup orig tuple for IPv6 SNAT
nf_sk_lookup_slow_v4 does the conntrack lookup for IPv4 packets to restore the original 5-tuple in case of SNAT, to be able to find the right socket (if any). Then socket_match() can correctly check whether the socket was transparent.
However, the IPv6 counterpart (nf_sk_lookup_slow_v6) lacks this conntrack lookup, making xt_socket fail to match on the socket when the packet was SNATed. Add the same logic to nf_sk_lookup_slow_v6.
IPv6 SNAT is used in Kubernetes clusters for pod-to-world packets, as pods' addresses are in the fd00::/8 ULA subnet and need to be replaced with the node's external address. Cilium leverages Envoy to enforce L7 policies, and Envoy uses transparent sockets. Cilium inserts an iptables prerouting rule that matches on `-m socket --transparent` and redirects the packets to localhost, but it fails to match SNATed IPv6 packets due to that missing conntrack lookup.
Patch / fix
- Linux Linux 5.4.292, 5.10.236, 5.15.180, 6.1.133, 6.6.86, 6.12.22, 6.13.10, 6.14.1, 6.15
- linux Debian 12 6.1.133-1
- linux Debian 14, Debian 13 6.12.22-1
debian advisories DEBIAN-CVE-2025-22021
- linux Ubuntu 22.04 LTS 5.15.0-142.152
- linux Ubuntu 24.04 LTS 6.8.0-86.87
- linux-aws Ubuntu 22.04 LTS 5.15.0-1086.93
- linux-aws Ubuntu 24.04 LTS 6.8.0-1041.43
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1085.94
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1042.45
- linux-gke Ubuntu 22.04 LTS 5.15.0-1083.89
- linux-gke Ubuntu 24.04 LTS 6.8.0-1038.43
ubuntu advisories UBUNTU-CVE-2025-22021
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- dtb-aarch64 openSUSE Leap 15.6 6.4.0-150600.23.53.1
- kernel-64kb SLE Module for Basesystem 15 SP6, openSUSE Leap 15.6 6.4.0-150600.23.53.1
- kernel-syms SLE Module for Development Tools 15 SP6, openSUSE Leap 15.6 6.4.0-150600.23.53.1
- kernel-obs-qa openSUSE Leap 15.6 6.4.0-150600.23.53.1
- kernel-source SLE Module for Development Tools 15 SP6, SLE Module for Basesystem 15 SP6, openSUSE Leap 15.6 6.4.0-150600.23.53.1
- kernel-default SLE Workstation Extension 15 SP6, SLE Module for Legacy 15 SP6, SLE Module for Basesystem 15 SP6 +3 more 6.4.0-150600.23.53.1
- kernel-kvmsmall openSUSE Leap 15.6 6.4.0-150600.23.53.1
- kernel-zfcpdump SLE Module for Basesystem 15 SP6, openSUSE Leap 15.6 6.4.0-150600.23.53.1
suse advisories SUSE-SU-2025:02000-1SUSE-SU-2025:01983-1SUSE-SU-2025:01972-1SUSE-SU-2025:20413-1SUSE-SU-2025:01967-1SUSE-SU-2025:01965-1
- git.kernel.org/stable/c/6488b96a79a26e19100ad872622f04e93b638d7f commit
- git.kernel.org/stable/c/58ab63d3ded2ca6141357a2b24eee8453d0f871d commit
- git.kernel.org/stable/c/1ca2169cc19dca893c7aae6af122852097435d16 commit
- git.kernel.org/stable/c/1ec43100f7123010730b7ddfc3d5c2eac19e70e7 commit
- git.kernel.org/stable/c/5251041573850e5020cd447374e23010be698898 commit
- git.kernel.org/stable/c/2bb139e483f8cbe488d19d8c1135ac3615e2668c commit
- git.kernel.org/stable/c/41904cbb343d115931d6bf79aa2c815cac4ef72b commit
- git.kernel.org/stable/c/221c27259324ec1404f028d4f5a0f2ae7f63ee23 commit
- git.kernel.org/stable/c/932b32ffd7604fb00b5c57e239a3cc4d901ccf6e commit
Is CVE-2025-22021 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-22021 updated cvss 5.5
kernel: netfilter: socket: Lookup orig tuple for IPv6 SNAT
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 25d ago
Exploit prediction
0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/6488b96a79a26e19100ad872622f04e93b638d7f
patch
-
git.kernel.org
/stable/c/58ab63d3ded2ca6141357a2b24eee8453d0f871d
patch
-
git.kernel.org
/stable/c/1ca2169cc19dca893c7aae6af122852097435d16
patch
-
git.kernel.org
/stable/c/1ec43100f7123010730b7ddfc3d5c2eac19e70e7
patch
-
git.kernel.org
/stable/c/5251041573850e5020cd447374e23010be698898
patch
-
git.kernel.org
/stable/c/2bb139e483f8cbe488d19d8c1135ac3615e2668c
patch
-
git.kernel.org
/stable/c/41904cbb343d115931d6bf79aa2c815cac4ef72b
patch
-
git.kernel.org
/stable/c/221c27259324ec1404f028d4f5a0f2ae7f63ee23
patch
-
git.kernel.org
/stable/c/932b32ffd7604fb00b5c57e239a3cc4d901ccf6e
patch
- lists.debian.org /debian-lts-announce/2025/05/msg00045.html
- lists.debian.org /debian-lts-announce/2025/05/msg00030.html
Sources
- CVE List CVE-2025-22021
- NVD CVE-2025-22021
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.