CVE-2026-72072

Description

A flaw was found in the Linux kernel's MACsec (Media Access Control Security) component. A race condition during the deletion of an offloaded MACsec RX Security Channel (SC) allows the RX datapath to access and operate on memory that has already been freed. This use-after-free vulnerability can lead to system instability or a denial of service.

Statement

A use-after-free can occur in the mlx5e MACsec RX offload path when RX SC deletion races with packet processing. The delete path used metadata_dst_free and could free the per SC metadata_dst without respecting dst references, while mlx5e_macsec_offload_handle_rx_skb() could already have loaded the SC through xa_load() under rcu_read_lock() and then attach the dst to an skb. This can lead to a kernel crash and in the worst case may create a memory corruption condition in the networking datapath. For the CVSS the PR:L is used for the paranoid score because delegated CAP_NET_ADMIN, container root, or a network management service account may be enough to delete or reconfigure MACsec RX SC state in some deployments. The issue is not Internet routed AV:N and is better treated as adjacent network plus local control plane exposure because MACsec operates at L2 and requires mlx5e MACsec offload to be configured. Impact is at least denial of service via kernel crash and in worst case may allow confidentiality or integrity impact due to UAF based memory corruption.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.3N/A7.8
Attack VectorNetworkN/ALocal
Attack ComplexityHighN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

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

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

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.