CVE-2021-22555 is a heap out-of-bounds write (CWE-787) in the Linux kernel's netfilter x_tables code, present since 2.6.19, that a local user can turn into root through a user namespace. NVD scores it 7.8. CISA lists it as exploited since 2025-10-06. Fixed in 5.10.31, 5.4.113, 4.19.188 and the other stable releases.
Vulnerability summary
CVSS base score
7.8
High severity
EPSS score (FIRST)
78.7%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
Yes
Listed as known exploited
Published
Vulnerability ID: CVE-2021-22555 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Linux kernel (netfilter x_tables) | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 2.6.19 to before 4.4.267, 4.5 to before 4.9.267, 4.10 to before 4.14.231, 4.15 to before 4.19.188, 4.20 to before 5.4.113, 5.5 to before 5.10.31, 5.11 to before 5.12 (NVD) |
| Debian linux | pkg:deb/debian/linux | Fixed in 4.9.272-1 (stretch), 4.19.194-1 (buster), 5.10.38-1 (unstable) (Debian security tracker) |
| Siemens SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (GNU/Linux subsystem) | — | Listed for firmware V2.9.3 and V2.9.4; not in the V3.0 list (Siemens SSB-439005) |
| Google Pixel (kernel, netfilter) | — | Fixed at security patch level 2021-10-05 or later (Pixel Update Bulletin October 2021, A-184847809) |
What does this mean for affected devices?
CVE-2021-22555 is a heap out-of-bounds write (CWE-787) in net/netfilter/x_tables.c, the shared code behind iptables, ip6tables and arptables in the Linux kernel. Google, the CNA, describes it as affecting "Linux since v2.6.19-rc1" and allowing an attacker "to gain privileges or cause a DoS (via heap memory corruption) through user name space". Google's security-research advisory GHSA-xxx5-8mvq-3528 places the bug in the compat IPT_SO_SET_REPLACE/IP6T_SO_SET_REPLACE setsockopt path used by 32-bit processes, where xt_compat_target_from_user() zeroes padding past the end of the allocated ruleset. NVD's Primary score is 7.8, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, with CWE-787. Google's CNA score is 8.3, CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H (NVD, CVE record).
Which kernel versions are affected?
NVD's CPE ranges start at 2.6.19 and end before 4.4.267, 4.9.267, 4.14.231, 4.19.188, 5.4.113 and 5.10.31; the 5.11 series is affected up to 5.12. The fix is commit b29c457a6511, "netfilter: x_tables: fix compat match/target pad out-of-bound write", which zeroes the whole ruleset blob up front. Its Fixes: tag points to the 2006 commit 9fa492cdc160 that introduced the bug, so the second git.kernel.org link in the CISA KEV notes is the origin, not a fix. Google's advisory gives 2021-04-06 as the report date, 2021-04-13 as the fix date and 2021-07-07 as disclosure. Debian's security tracker lists the linux package fixed in 4.9.272-1 for stretch, 4.19.194-1 for buster and 5.10.38-1 in unstable.
Which devices are affected?
Any Linux-based device on an unfixed kernel with the x_tables compat path, where a local process can reach it. Siemens bulletin SSB-439005 lists CVE-2021-22555 among the "relevant during runtime" vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP, firmware V2.9.3 and V2.9.4; the V3.0 list does not include it. Siemens recommends defence in depth and to "only build and run applications from trusted sources". Google's Pixel Update Bulletin for October 2021 fixed it on Pixel devices at patch level 2021-10-05 (A-184847809, EoP, Moderate, netfilter). NVD's configuration also lists NetApp HCI, SolidFire and storage-controller firmware and Broadcom Fabric OS. The ENISA EUVD guide uses this CVE as its CVE-to-EUVD mapping example (EUVD-2021-9696).
How do you fix CVE-2021-22555?
Move the kernel to at least the fixed release of its stable branch (4.4.267, 4.9.267, 4.14.231, 4.19.188, 5.4.113, 5.10.31) or 5.12 and later, or backport commit b29c457a6511. On the Siemens MFP CPU, follow SSB-439005's mitigations and move to the current firmware. The CNA description names user namespaces as the route to the bug, so where unprivileged user namespaces are not needed, restricting them reduces exposure until the kernel is updated.
Is CVE-2021-22555 exploited?
Yes. CISA added it to the KEV catalog on 2025-10-06 with a due date of 2025-10-27; known ransomware campaign use is Unknown, as of 2026-11-19 (catalog version 2026.11.18). Google's advisory states it can be used to achieve "kernel code execution while bypassing KASLR, SMAP and SMEP". FIRST EPSS gives it 0.78684, the 99.6th percentile, in the 2026-11-18 dataset (CISA KEV, FIRST EPSS). Related KEV-listed kernel CVEs include CVE-2024-53104 in uvcvideo and CVE-2025-39964 in af_alg.
Evidence
- NVD: status Analyzed; [email protected] Primary CVSS 3.1 7.8 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; [email protected] Secondary 8.3 AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H; CWE-787; CPE linux_kernel 2.6.19 to before 4.4.267, 4.5-4.9.267, 4.10-4.14.231, 4.15-4.19.188, 4.20-5.4.113, 5.5-5.10.31, 5.11-5.12, plus NetApp and Broadcom Fabric OS entries; published 2021-07-07; read from cached API response 2026-11-19. — NVD
- CVE record (CNA Google, PUBLISHED 2021-07-07): title 'Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACE'; affected from 2.6.19-rc1; CNA CVSS 3.1 8.3; CWE-787; CISA ADP SSVC Exploitation active and KEV dateAdded 2025-10-06. — CVE.org
- GHSA-xxx5-8mvq-3528: compat IPT_SO_SET_REPLACE/IP6T_SO_SET_REPLACE; out-of-bounds memset in xt_compat_target_from_user; exploitable for kernel code execution bypassing KASLR, SMAP and SMEP; reported 2021-04-06, fixed 2021-04-13, disclosed 2021-07-07. — Google security-research
- Commit b29c457a6511 'netfilter: x_tables: fix compat match/target pad out-of-bound write' (Florian Westphal, 2021-04-07), Reported-by Andy Nguyen, Fixes: 9fa492cdc160c ('[NETFILTER]: x_tables: simplify compat API', 2006). — git.kernel.org
- Debian: linux fixed stretch 4.9.272-1, buster 4.19.194-1, unstable 5.10.38-1. — Debian security tracker
- SSB-439005 V5.9 (2024-02-13, no longer maintained): CVE-2021-22555 listed as relevant during runtime for the GNU/Linux subsystem of S7-1500 CPU 1518(F)-4 PN/DP MFP firmware V2.9.4 and V2.9.3 (added in V3.6, 2021-08-10); not in the V3.0 list; mitigations: defence in depth, only build and run applications from trusted sources. — Siemens ProductCERT
- Pixel Update Bulletin October 2021 (published 2021-10-04): CVE-2021-22555, A-184847809, upstream kernel, EoP, Moderate, netfilter; patch level 2021-10-05 or later addresses it on Google devices. — Android (Pixel Update Bulletin)
- CISA KEV catalog version 2026.11.18: Linux Kernel Heap Out-of-Bounds Write Vulnerability, dateAdded 2025-10-06, dueDate 2025-10-27, knownRansomwareCampaignUse Unknown; checked 2026-11-19. — CISA KEV
- EPSS 0.78684, percentile 0.99595, dataset 2026-11-18, read 2026-11-19. — FIRST EPSS

Related advisories
Sources
- NVD
- CVE.org record CVE-2021-22555 (CNA: Google)
- Google security-research GHSA-xxx5-8mvq-3528
- Linux kernel fix commit b29c457a6511
- Debian security tracker: CVE-2021-22555
- Siemens ProductCERT SSB-439005: GNU/Linux subsystem of SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP < V3.1
- Pixel Update Bulletin: October 2021
- CISA KEV
- FIRST EPSS
Frequently asked questions
Which kernel versions fix CVE-2021-22555?
4.4.267, 4.9.267, 4.14.231, 4.19.188, 5.4.113, 5.10.31 and 5.12 onward; the bug dates from 2.6.19. Each stable branch has its own fixed release, so a 5.4.120 kernel is fixed (per NVD's CPE configuration).
Does CVE-2021-22555 affect Siemens PLCs?
Siemens lists it for the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP, firmware V2.9.3 and V2.9.4, and recommends defence in depth and running only trusted applications. The V3.0 list does not include it (per Siemens SSB-439005).
Why does Google score it 8.3 when NVD says 7.8?
Google's CNA vector uses an adjacent attack vector with high complexity, no privileges and changed scope, while NVD scores it as a local attack needing low privileges (per NVD and the Google CNA record on CVE.org).
Is CVE-2021-22555 exploited in the wild?
Yes. CISA added it to the KEV catalog on 2025-10-06, with ransomware use listed as Unknown, as of 2026-11-19 (catalog version 2026.11.18). FIRST EPSS gives it 0.78684, the 99.6th percentile, in the 2026-11-18 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?