Skip to main content
Mallory
High

Linux kernel nf_tables use-after-free in nft_map_catchall_activate

IdentifiersCVE-2026-23111CWE-416· Use After Free

CVE-2026-23111 is a local use-after-free vulnerability in the Linux kernel nf_tables subsystem. The root cause is an inverted activity/genmask check in nft_map_catchall_activate(), the abort-path callback used to reactivate catchall map elements after a failed nftables transaction. Due to the incorrect negation, the function skips inactive catchall elements that should be restored and instead processes already-active ones. As a result, when a DELSET operation is aborted, nft_setelem_data_activate() is not invoked for the catchall element. For NFT_GOTO verdict elements, nft_data_hold() is therefore not called to restore the referenced chain's use count. Repeated abort cycles can permanently decrement chain->use until it reaches zero, after which DELCHAIN can free the chain while catchall verdict elements still retain references to it, creating a dangling pointer and use-after-free condition. Public reporting indicates this can be exploited by an unprivileged local user to obtain root privileges and escape container or namespace isolation on systems exposing the relevant kernel attack surface.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can yield local privilege escalation to root and, in containerized environments, namespace/container escape. The vulnerability also permits kernel memory corruption through a dangling chain reference in nf_tables, which can lead to arbitrary kernel code execution in practice. At minimum, the flaw can also cause kernel instability or denial of service if the use-after-free is triggered without reliable exploitation.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by disabling or restricting unprivileged user namespaces where operationally feasible, for example via kernel.unprivileged_userns_clone=0 on platforms that support it. Limit untrusted local users' ability to reach nftables functionality, including in containers or sandboxed workloads. Prioritize systems that allow untrusted code execution, multi-user access, or container workloads with user namespace creation. These measures are partial mitigations only and do not replace installing a fixed kernel.

Remediation

Patch, then assume compromise.

Apply a Linux kernel update containing the upstream fix for CVE-2026-23111. The fix corrects nft_map_catchall_activate() by removing the erroneous negation so that active elements are skipped and inactive catchall elements are properly reactivated during transaction abort handling, restoring the chain reference count correctly. Deploy vendor-supplied patched kernels from the relevant distribution and reboot into the updated kernel. Where available, use the upstream patch referenced in public reporting as commit f41c5d1 or the corresponding backport from your distribution.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
DebianLinuxapplication
LinuxLinux Kerneloperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity15

Community discussion across Reddit, Mastodon, and other social sources.