CVE-2026-53212
Analyzed
Analyzed - Analysis Complete
Use-After-Free in Linux Kernel nft_tunnel
Vulnerability report for CVE-2026-53212, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.
Publication date: 2026-06-25
Last updated on: 2026-07-02
Assigner: kernel.org
Description
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.
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | From 5.16 (inc) to 6.1.176 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.143 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.210 (exc) |
| linux | linux_kernel | From 4.19 (inc) to 5.10.259 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.36 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.94 (exc) |
| linux | linux_kernel | From 6.19 (inc) to 7.0.13 (exc) |
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | 7.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |