netfilter: nft_tunnel: fix use-after-free on object destroy
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From af308b94a2a4a5a27bec9028354c4df444a7c8ba · fixed in 349df61526d2e39decc685d246202e3e284cfe05; From af308b94a2a4a5a27bec9028354c4df444a7c8ba · fixed in 55b79b1ae42372012413ce0413181d26679b17ef; From af308b94a2a4a5a27bec9028354c4df444a7c8ba · fixed in 5e9ee18b27fde88cb6148202b33916c66693fe82; From af308b94a2a4a5a27bec9028354c4df444a7c8ba · fixed in 8767fe4079affa74314d7eb3220e700150289842; From af308b94a2a4a5a27bec9028354c4df444a7c8ba · fixed in fda6573a46ad24f35348e024905ee5bdf729797e; From af308b94a2a4a5a27bec9028354c4df444a7c8ba · fixed in 941d7394efda5e054e2d6f3e0dd0f6a9ba19aaa3; From af308b94a2a4a5a27bec9028354c4df444a7c8ba · fixed in f9a0e4b61054cde89a2a77845293c726cc07cc43; From af308b94a2a4a5a27bec9028354c4df444a7c8ba · fixed in c32b26aaa2f9216520a38b3f4bfeec846eb3eb8a
- Linux Linux
4.19
- KernelLinux
From 4.19.0 · fixed in 5.10.259; From 5.11.0 · fixed in 5.15.210; From 5.16.0 · fixed in 6.1.176; From 6.2.0 · fixed in 6.6.143; From 6.7.0 · fixed in 6.12.94; From 6.13.0 · fixed in 6.18.36; From 6.19.0 · fixed in 7.0.13
References 8
git.kernel.org
- stable/c/349df61526d2e39decc685d246202e3e284cfe05
- stable/c/55b79b1ae42372012413ce0413181d26679b17ef
- stable/c/5e9ee18b27fde88cb6148202b33916c66693fe82
- stable/c/8767fe4079affa74314d7eb3220e700150289842
- stable/c/fda6573a46ad24f35348e024905ee5bdf729797e
- stable/c/941d7394efda5e054e2d6f3e0dd0f6a9ba19aaa3
- stable/c/f9a0e4b61054cde89a2a77845293c726cc07cc43
- stable/c/c32b26aaa2f9216520a38b3f4bfeec846eb3eb8a