Vulnerability · Published Aug 15, 2026 · Assigned by Linux
CVE-2026-72072net/mlx5e: macsec: fix use-after-free of metadata_dst on RX SC delete
High 7.8
In plain English
A high-severity use-after-free in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 7% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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).
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| AlmaLinux:9 | kernel | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-64k | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-64k-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-64k-debug | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-64k-debug-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-64k-debug-devel | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-64k-debug-modules | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-64k-devel | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-64k-devel-matched | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-64k-modules | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-64k-modules-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-64k-modules-extra | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-abi-stablelists | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-cross-headers | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-debug | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-debug-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-debug-devel | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-debug-devel-matched | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-debug-modules | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-debug-modules-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-debug-modules-extra | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-debug-uki-virt | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-devel | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-devel-matched | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-doc | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-headers | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-modules | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-modules-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-modules-extra | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-64k | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-64k-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-64k-debug | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-64k-debug-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-64k-debug-devel | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-64k-debug-modules | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-64k-debug-modules-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-64k-debug-modules-extra | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-64k-devel | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-64k-modules | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-64k-modules-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-64k-modules-extra | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-debug | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-debug-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-debug-devel | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-debug-modules | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-debug-modules-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-debug-modules-extra | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-devel | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-modules | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-modules-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-rt-modules-extra | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-tools | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-tools-libs | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-tools-libs-devel | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-uki-virt | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-uki-virt-addons | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-zfcpdump | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-zfcpdump-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-zfcpdump-devel | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-zfcpdump-devel-matched | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-zfcpdump-modules | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-zfcpdump-modules-core | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | kernel-zfcpdump-modules-extra | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | libperf | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | perf | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | python3-perf | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | rtla | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| AlmaLinux:9 | rv | 5.14.0-687.50.1.el9_8 | ALSA-2026:70459 |
| Debian:12 | linux | 6.1.180-1 | DEBIAN-CVE-2026-72072 |
| Debian:13 | linux | 6.12.100-1 | DEBIAN-CVE-2026-72072 |
| Debian:14 | linux | 7.1.5-1 | DEBIAN-CVE-2026-72072 |
| Rocky Linux:9 | kernel | 0:5.14.0-687.50.1.el9_8 | RLSA-2026:70459 |
| Ubuntu:24.04:LTS | linux | 6.8.0-147.147 | UBUNTU-CVE-2026-72072 |
| Ubuntu:26.04:LTS | linux | 7.0.0-38.38 | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1067.70 | UBUNTU-CVE-2026-72072 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1014.14 | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-aws-7.0 | 7.0.0-1014.14~24.04.1 | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1071.79 | UBUNTU-CVE-2026-72072 |
| Ubuntu:26.04:LTS | linux-azure | 7.0.0-1017.17 | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-azure-7.0 | 7.0.0-1017.17~24.04.1 | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1069.76 | UBUNTU-CVE-2026-72072 |
| Ubuntu:26.04:LTS | linux-azure-fde | 7.0.0-1016.16 | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.17 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1016.16~24.04.1 | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1071.79 | UBUNTU-CVE-2026-72072 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1014.14 | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-gcp-7.0 | 7.0.0-1014.14~24.04.1 | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1066.74 | UBUNTU-CVE-2026-72072 |
| Ubuntu:26.04:LTS | linux-gke | 7.0.0-1008.9 | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1052.56 | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-38.38~24.04.4 | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1067.68 | UBUNTU-CVE-2026-72072 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1015.15 | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-147.147.1 | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:26.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-nvidia-7.0 | 7.0.0-1024.25~24.04.1 | UBUNTU-CVE-2026-72072 |
| Ubuntu:26.04:LTS | linux-nvidia-bos | 7.0.0-2022.23 | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1036.39 | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:26.04:LTS | linux-oem-7.0 | 7.0.0-1015.15 | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1064.67 | UBUNTU-CVE-2026-72072 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1013.13 | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-oracle-7.0 | 7.0.0-1013.13~24.04.1 | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:26.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:26.04:LTS | linux-realtime | 7.0.0-38.38.1 | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:26.04:LTS | linux-riscv | 7.0.0-38.38.1 | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-riscv-7.0 | 7.0.0-38.38.1~24.04.1 | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-vmware | 6.8.0-1008.8 | UBUNTU-CVE-2026-72072 |
| Ubuntu:24.04:LTS | linux-xilinx | no fix listed | UBUNTU-CVE-2026-72072 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | b7c9400cbc48c3713190b3bce4e0c87e924e4104 – before b1a4d0c568bbb52c7c04f4fce3c097dae89ed6cbb7c9400cbc48c3713190b3bce4e0c87e924e4104 – before 218cc15a4c907659ad4b0e68c535c61594311205b7c9400cbc48c3713190b3bce4e0c87e924e4104 – before 4a5073b7b30243658f58b2d2d35a823da7fd34d9b7c9400cbc48c3713190b3bce4e0c87e924e4104 – before ed3cc4218070d6b98bf5fb456dccae424fd38c4fb7c9400cbc48c3713190b3bce4e0c87e924e4104 – before 088873af13590ebde10de2ade847f57a05ec61c6b7c9400cbc48c3713190b3bce4e0c87e924e4104 – before de74d8fd10291763d97b218f09adcc7513c975e4 |
| Linux | Linux | 6.1 |
Weakness: CWE-416 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
References
- https://git.kernel.org/stable/c/b1a4d0c568bbb52c7c04f4fce3c097dae89ed6cb
- https://git.kernel.org/stable/c/218cc15a4c907659ad4b0e68c535c61594311205
- https://git.kernel.org/stable/c/4a5073b7b30243658f58b2d2d35a823da7fd34d9
- https://git.kernel.org/stable/c/ed3cc4218070d6b98bf5fb456dccae424fd38c4f
- https://git.kernel.org/stable/c/088873af13590ebde10de2ade847f57a05ec61c6
- https://git.kernel.org/stable/c/de74d8fd10291763d97b218f09adcc7513c975e4