CVE-2026-53212: Linux Kernel Netfilter Tunnel Use-After-Free Vulnerability (CVSS 7.8)
A use-after-free vulnerability exists in the Linux kernel's netfilter tunnel implementation. When the tunnel object is destroyed, the code improperly frees memory without accounting for packets that may still hold references to that memory. If packets queued in network discipline systems (like netem) eventually attempt to release their references, they operate on already-freed memory, causing a kernel crash or potential code execution. The fix replaces an unsafe free operation with proper reference-counting semantics.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.8 HIGH · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-416
- Affected products
- 7 configuration(s)
- Published / Modified
- 2026-06-25 / 2026-07-02
NVD description (verbatim)
In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_tunnel: fix use-after-free on object destroy nft_tunnel_obj_destroy() calls metadata_dst_free() which directly kfree()s the metadata_dst, ignoring the dst_entry refcount. Packets that took a reference via dst_hold() in nft_tunnel_obj_eval() and are still queued (e.g. in a netem qdisc) are left with a dangling pointer. When these packets are eventually dequeued, dst_release() operates on freed memory. Replace metadata_dst_free() with dst_release() so the metadata_dst is freed only after all references are dropped. The dst subsystem already handles metadata_dst cleanup in dst_destroy() when DST_METADATA is set.
8 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-53212 is a use-after-free (CWE-416) flaw in nft_tunnel_obj_destroy() within the Linux kernel's netfilter subsystem. The function calls metadata_dst_free() to directly kfree() the metadata_dst structure while ignoring the dst_entry reference count. During normal packet processing in nft_tunnel_obj_eval(), packets call dst_hold() to increment the reference count. If these packets remain queued in network disciplines (e.g., netem) when the tunnel object is destroyed, they retain dangling pointers to freed memory. Subsequent dst_release() calls on dequeued packets operate on freed memory, causing a use-after-free condition. The remediation replaces metadata_dst_free() with dst_release(), allowing the dst subsystem to properly manage cleanup when the DST_METADATA flag is set and the reference count reaches zero.
Business impact
This vulnerability enables denial of service attacks on Linux systems running affected kernel versions. A local attacker with limited privileges can trigger the use-after-free condition, resulting in kernel panic and system unavailability. The HIGH severity rating reflects local attack surface, but the impact—complete loss of system availability—is critical for production environments. Systems relying on netfilter-based tunneling for network policy enforcement face operational risk until patched. No direct data confidentiality or integrity breach is evident, but kernel exploitation could theoretically lead to privilege escalation.
Affected systems
The Linux kernel is affected across multiple stable and development versions. The vulnerability specifically impacts systems using the netfilter tunnel (nft_tunnel) module, which is common in network policy, packet filtering, and tunneling setups. Distributions shipping recent kernel versions without this specific fix are vulnerable. Verify your kernel version against the official Linux kernel security advisories and your distribution's patch status.
Exploitability
This vulnerability requires local system access (non-remote) and is triggered through standard network packet processing. The attack vector involves queuing packets in a network discipline such as netem and then triggering tunnel object destruction, causing the use-after-free when packets are dequeued. While not trivial, the requirements (local access, ability to queue packets and destroy objects) are achievable by unprivileged users on systems where netfilter tunneling is enabled. The condition is reliably reproducible under specific timing, making exploitation practical. The vulnerability is not currently tracked in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Remediation
Update to a Linux kernel version that includes the fix for CVE-2026-53212. The remediation involves replacing the metadata_dst_free() call with dst_release(), ensuring proper reference counting and memory management through the dst subsystem. Verify the specific patched kernel version against your distribution's security advisories and kernel release notes. For systems unable to immediately patch, disable or restrict netfilter tunnel functionality if operationally feasible.
Patch guidance
Apply the latest kernel security update from your Linux distribution. Confirm that the patch date (or kernel version inclusion date) is on or after the vulnerability publish date (2026-06-25). Kernel maintainers typically backport fixes to stable and LTS branches; verify against your specific branch (e.g., 6.1.x, 6.6.x, 6.9.x, or mainline). Test the patched kernel in a staging environment to ensure no regression in netfilter or tunnel functionality before production deployment. Coordinate patching with your scheduled maintenance windows and consider kexec or live kernel patching if available in your distribution.
Detection guidance
Monitor kernel logs for BUG, KASAN (Kernel Address Sanitizer), or memory corruption warnings related to metadata_dst or dst_release operations. Network monitoring tools tracking tunnel object lifecycle events may reveal abnormal destruction patterns. Test environments with netem or similar traffic discipline tools can reproduce the condition; use CONFIG_KASAN=y builds to catch use-after-free violations early. Host-based intrusion detection should flag kernel crash events and unexpected system reboots potentially triggered by the vulnerability.
Why prioritize this
Prioritize this vulnerability HIGH due to its local denial-of-service impact, direct kernel memory safety violation, and the prevalence of netfilter in production environments. Although remote exploitation is not possible, the ability to crash the entire kernel from an unprivileged account poses significant availability risk. Prompt patching is essential for production systems.
Risk score, explained
The CVSS 3.1 score of 7.8 reflects a HIGH severity local attack requiring limited privileges, no user interaction, and no scope boundary crossing. The vulnerability directly impacts system availability (A:H) and potential integrity (I:H) through kernel exploitation, with confidentiality exposure (C:H) possible through memory disclosure. The access complexity is low (AC:L) because standard network packet handling can trigger the condition. This score appropriately ranks the risk as significant for production systems despite the local-only attack vector.
Frequently asked questions
Can this vulnerability be exploited remotely?
No. CVE-2026-53212 requires local system access and the ability to queue packets in a network discipline while controlling tunnel object lifecycle. It is not remotely exploitable.
Which distributions are affected?
All Linux distributions shipping unpatched kernel versions are affected. Check your distribution's security advisories for specific affected kernel versions and patch availability. Most major distributions (Red Hat, Debian, Ubuntu, SUSE, etc.) have released patches; verify your system's current kernel version.
Does disabling netfilter prevent exploitation?
Disabling the nft_tunnel module prevents the specific vulnerability from being triggered. However, this may impact network policy enforcement and tunnel functionality. Use this as a temporary mitigation only while awaiting kernel patches.
What is the root cause of this vulnerability?
The root cause is improper memory management—freeing a reference-counted object (metadata_dst) without respecting its reference count. Packets holding references to the freed memory later crash when attempting to decrement the reference count. The fix properly delegates cleanup to the reference-counting system.
This analysis is based on publicly disclosed information as of the publication date. Exploit code is not provided. Readers should verify all patch version numbers, affected product lists, and remediation steps against official vendor advisories and their specific system configurations. SEC.co makes no warranty regarding the completeness or accuracy of third-party vulnerability data. Test all patches in non-production environments before deployment. Source: NVD (public-domain), retrieved 2026-08-03. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-10001HIGHChrome Sandbox Escape via PerformanceManager Use-After-Free
- CVE-2026-10002HIGHGoogle Chrome PDFium Use-After-Free Vulnerability (CVSS 8.8)
- CVE-2026-10003HIGHChrome Use-After-Free Code Execution Vulnerability Analysis
- CVE-2026-10007HIGHChrome Use-After-Free in SVG Arbitrary Code Execution (CVSS 8.8)
- CVE-2026-10012HIGHChrome Skia Use-After-Free Sandbox Escape (v148.0.7778.216)
- CVE-2026-10013HIGHUse-After-Free in Chrome WebCodecs – Patch Guide & Risk Assessment
- CVE-2026-10016HIGHUse-After-Free in Chrome DOM – Sandbox Code Execution Vulnerability
- CVE-2026-10882HIGHCritical Chrome Use-After-Free RCE Vulnerability – Exploit Details & Patch Guidance