Skip to main content
← All vulnerabilities
CVE-2021-22555

Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACE

Affects Linux kernels from 2.6.19-rc1 onward when IPT_SO_SET_REPLACE or IP6T_SO_SET_REPLACE runs in compat mode. Fixed in 5.10.31, 5.4.113, 4.19.188, 4.14.231, 4.9.267 and 4.4.267.

Published
Last modified
published
Listed in CISA KEV
Actively exploited
Fix
Fixed in 5.10.31, 5.4.113, 4.19.188, 4.14.231, 4.9.267, and 1 more
None on Exploit-DB, Metasploit or GitHub

Summary

The Linux kernel's Netfilter x_tables component, which handles IPv6 packet filtering rules, is affected by this flaw. An attacker could exploit it through user namespaces to gain elevated privileges or crash the system by corrupting heap memory.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original description

A heap out-of-bounds write affecting Linux since v2.6.19-rc1 was discovered in net/netfilter/x_tables.c. This allows an attacker to gain privileges or cause a DoS (via heap memory corruption) through user name space

Timeline

  1. CVE published
  2. Added to CISA KEV

    CISA has evidence of exploitation in the wild

  3. CISA remediation deadline

    Due date for US federal agencies to patch

  4. Record last updated
  5. EPSS reached 10%

    FIRST estimates at least a 10% chance of exploitation in the next 30 days

Affected versions

  • n/a Linux Kernel

    From 2.6.19-rc1 · fixed in unspecified

References 9

GitHub · google/security-research

git.kernel.org

packetstormsecurity.com

security.netapp.com

FAQ

Questions about CVE-2021-22555

What does this mean?

A heap out-of-bounds write in the Netfilter IP6T_SO_SET_REPLACE code corrupts heap memory. Per the advisory, local users can use it to gain privileges or cause a denial of service via a user namespace.Source: github.com

Am I affected, and how do I check?

Linux kernel versions from 2.6.19-rc1 onward are affected when IPT_SO_SET_REPLACE or IP6T_SO_SET_REPLACE is called in compat mode. Check the kernel version with uname -r; the facts give no setting for compat mode.Source: github.com

What should I do about it?

Move to a fixed stable release on the matching branch: 5.10.31, 5.4.113, 4.19.188, 4.14.231, 4.9.267 or 4.4.267. The facts list no workaround.Source: github.com

Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-10-06, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data