Skip to main content
Mallory
High

Linux kernel nf_tables catchall activation use-after-free local privilege escalation

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

CVE-2026-23111 is a use-after-free in the Linux kernel nf_tables subsystem caused by an inverted activity/genmask check in nft_map_catchall_activate(). During abort handling for a failed nftables transaction, catchall map elements that were deactivated earlier should be reactivated. Due to the inverted conditional, the function skips inactive catchall elements and processes active ones, the opposite of the required logic. 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 in nf_tables.

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 allows a local unprivileged attacker to achieve kernel-level privilege escalation to root. Public reporting also states the flaw can be used for container or namespace escape because exploitation can culminate in kernel code execution and restoration of init credentials and namespaces. In addition to privilege escalation, the bug can also plausibly cause kernel instability or denial of service through use-after-free-triggered crashes.

Mitigation

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

Where patching cannot be performed immediately, restrict or disable unprivileged user namespaces if operationally feasible, for example via kernel.unprivileged_userns_clone=0 on platforms that support that control. Reduce exposure of nf_tables functionality to untrusted local users and untrusted container workloads, and prioritize systems that permit local code execution by non-admin users or tenant-controlled containers. These 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 removes the incorrect negation in nft_map_catchall_activate() so active elements are skipped and inactive catchall elements are properly reactivated during transaction abort handling. Deploy vendor-supplied patched kernels for affected distributions and reboot systems after updating to ensure the fixed kernel is running.
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 activity10

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