VDB

CVE-2026-72072

CVE-2026-72072 PUBLISHED CVSS 7.8 HIGH

net/mlx5e: macsec: fix use-after-free of metadata_dst on RX SC delete

Reported by linux · Published August 15, 2026

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: macsec: fix use-after-free of metadata_dst on RX SC delete When an offloaded MACsec RX SC is deleted, macsec_del_rxsc_ctx() freed the per-SC metadata_dst with metadata_dst_free(), which kfree()s the object unconditionally and ignores the dst reference count. The RX datapath in mlx5e_macsec_offload_handle_rx_skb() looks up the SC under rcu_read_lock() via xa_load(), takes a reference with dst_hold() and attaches the dst to the skb with skb_dst_set(). A reader that already obtained the rx_sc pointer can race with the delete path and operate on freed memory. Fix the owner side by dropping the reference with dst_release() instead of freeing unconditionally, and convert the RX datapath to dst_hold_safe() so a reader racing the SC delete cannot attach a dst whose last reference was just dropped; only attach it when a reference was actually taken. mlx5e_macsec_add_rxsc() also published sc_xarray_element via xa_alloc() before rx_sc->md_dst was allocated and initialised, so a datapath reader that looked the SC up by fs_id could observe rx_sc with md_dst still NULL or, on weakly-ordered architectures, a non-NULL md_dst pointer whose contents were not yet visible. NULL-check the xa_load() result and md_dst on the datapath, and reorder add_rxsc() so the xa_alloc() publish happens only after md_dst is fully initialised; the xarray RCU publish then pairs with the rcu_read_lock()/xa_load() in the datapath. Note: macsec_del_rxsc_ctx() also kfree()s rx_sc->sc_xarray_element without an RCU grace period while the same datapath reads it under rcu_read_lock(); that is a separate pre-existing issue left to a follow-up patch. Found by 0sec automated security-research tooling (https://0sec.ai).

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel6.18-headersAmazon Linux1:6.18.41-94.142.amzn2023
kernelerrata.rockylinux.org5.14.0-687.50.1.el9
kernel-debug-develerrata.rockylinux.org5.14.0-687.50.1.el9
kernel-debuginfo-common-aarch64errata.rockylinux.org5.14.0-687.50.1.el9
kernel-rt-debug-develerrata.rockylinux.org5.14.0-687.50.1.el9
kernel-coreerrata.rockylinux.org5.14.0-687.50.1.el9
kernel-modules-extraerrata.rockylinux.org5.14.0-687.50.1.el9
kernel-rt-64k-debug-debuginfoerrata.rockylinux.org5.14.0-687.50.1.el9
rtlaerrata.rockylinux.org5.14.0-687.50.1.el9
python3-perferrata.rockylinux.org5.14.0-687.50.1.el9
kernel-debug-modules-coreerrata.rockylinux.org5.14.0-687.50.1.el9
kernel-64k-coreerrata.rockylinux.org5.14.0-687.50.1.el9

62 more packages have a fixed version. See every fix in Lookup.

Risk scores

CVSS 3.1
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

VendorProductVersions
LinuxLinuxb7c9400cbc48c3713190b3bce4e0c87e924e4104, b7c9400cbc48c3713190b3bce4e0c87e924e4104, b7c9400cbc48c3713190b3bce4e0c87e924e4104
LinuxLinux6.1, 0, 6.1.178
amazon:2023kernel6.18-headers0
amazon:2023kernel-modules-extra-common0
amazon:2023kernel6.12-modules-extra0
amazon:2023kernel6.180
amazon:2023kernel6.18-modules-extra0
amazon:2023kernel6.18-tools0
amazon:2023python3-perf6.120
amazon:2023perf6.180
amazon:2023bpftool6.120
amazon:2023kernel6.18-modules-extra-common0
amazon:2023python3-perf0
amazon:2023kernel-tools0
amazon:2023python3-perf6.180
amazon:2023kernel6.12-tools-devel0
amazon:2023kernel-livepatch-6.18.41-94.1420
amazon:2023kernel-tools-devel0
amazon:2023perf6.120
amazon:2023microvm-kernel6.180

…and 18 more

Timeline

  • Aug 15, 2026 Coalition ESS Score
  • Aug 15, 2026 CVE Published
  • Aug 19, 2026 Security Advisory
  • Aug 24, 2026 EPSS Score (13 in total, the first dated here)
  • Oct 7, 2026 Distribution Patch
  • Oct 19, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-72072
vulnetix vdb fixes CVE-2026-72072

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-72072/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›