Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 3 weeks ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
netfilter: nft_tunnel: fix use-after-free on object destroy

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.

Affected products

Linux
  • =<6.18.*
  • =<*
  • =<6.1.*
  • <8767fe4079affa74314d7eb3220e700150289842
  • =<6.6.*
  • <5e9ee18b27fde88cb6148202b33916c66693fe82
  • =<7.0.*
  • =<6.12.*
  • <941d7394efda5e054e2d6f3e0dd0f6a9ba19aaa3
  • <349df61526d2e39decc685d246202e3e284cfe05
  • <f9a0e4b61054cde89a2a77845293c726cc07cc43
  • <4.19
  • ==4.19
  • =<5.15.*
  • <55b79b1ae42372012413ce0413181d26679b17ef
  • <c32b26aaa2f9216520a38b3f4bfeec846eb3eb8a
  • =<5.10.*
  • <fda6573a46ad24f35348e024905ee5bdf729797e