Skip to main content
VulnerabilityPublished Updated

CVE-2026-53212: Linux kernel · netfilter: nft_tunnel: fix use-after-free on object destroy

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High · fixed in fda6573a46ad24f35348e024905ee5bdf729797e : patch Linux kernel soon.

Data as of 26 Oct 2026, 17:30 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in fda6573a46ad24f35348e024905ee5bdf729797e, f9a0e4b61054cde89a2a77845293c726cc07cc43, c32b26aaa2f9216520a38b3f4bfeec846eb3eb8a +5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ af308b94a2a4a5a27bec9028354c4df444a7c8ba, < fda6573a46ad24f35348e024905ee5bdf729797e
Fixed in
  • fda6573a46ad24f35348e024905ee5bdf729797e
LinuxLinuxAffected
  • ≥ af308b94a2a4a5a27bec9028354c4df444a7c8ba, < f9a0e4b61054cde89a2a77845293c726cc07cc43
Fixed in
  • f9a0e4b61054cde89a2a77845293c726cc07cc43
LinuxLinuxAffected
  • ≥ af308b94a2a4a5a27bec9028354c4df444a7c8ba, < c32b26aaa2f9216520a38b3f4bfeec846eb3eb8a
Fixed in
  • c32b26aaa2f9216520a38b3f4bfeec846eb3eb8a
LinuxLinuxAffected
  • ≥ af308b94a2a4a5a27bec9028354c4df444a7c8ba, < 8767fe4079affa74314d7eb3220e700150289842
Fixed in
  • 8767fe4079affa74314d7eb3220e700150289842
LinuxLinuxAffected
  • ≥ af308b94a2a4a5a27bec9028354c4df444a7c8ba, < 941d7394efda5e054e2d6f3e0dd0f6a9ba19aaa3
Fixed in
  • 941d7394efda5e054e2d6f3e0dd0f6a9ba19aaa3
LinuxLinuxAffected
  • ≥ af308b94a2a4a5a27bec9028354c4df444a7c8ba, < 349df61526d2e39decc685d246202e3e284cfe05
Fixed in
  • 349df61526d2e39decc685d246202e3e284cfe05

Description

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.

References

Community reviews

Loading reviews…