CVE-2026-64574
Description
A flaw was found in the Linux kernel's mac80211 Wi-Fi subsystem. When new Wi-Fi links are added, an error in the update process can cause debugfs entries to point to memory that has already been freed. A local attacker can exploit this use-after-free vulnerability by accessing these dangling debugfs entries, which can lead to a system crash and a denial of service.
Statement
A moderate-impact use-after-free flaw was found in the Linux kernel's mac80211 Wi-Fi subsystem as shipped in Red Hat Enterprise Linux and Red Hat In-Vehicle OS. When ieee80211_vif_update_links() adds new Wi-Fi links and the subsequent drv_change_vif_links() driver callback fails, which can occur at runtime on multi-link operation (MLO) capable drivers due to internal allocation, queue, or firmware command failures, the error path frees the newly allocated link containers without removing their per-link debugfs entries or stopping the links. The surviving debugfs files keep file->private_data pointing into the freed memory, so a local attacker who can read one of these dangling debugfs entries (for example link-1/txpower) triggers a use-after-free read in ieee80211_if_read_link(), causing a kernel panic and a denial of service.
The affected scope covers the kernel and kernel-rt components of Red Hat Enterprise Linux 8 (8.10 update stream), Red Hat Enterprise Linux 9 (9.4, 9.6, 9.8, and 9.9 streams), Red Hat Enterprise Linux 10 (10.0, 10.2, and 10.3 streams), and Red Hat In-Vehicle OS 2, including its kernel-ivos-qualcomm component; in these streams the fix is currently deferred. Earlier Red Hat Enterprise Linux streams (RHEL 6 ELS, RHEL 7 ELS, and the RHEL 8.4, 8.6, 8.8, and RHEL 9.2 update streams) are not affected because the code that registers the per-link debugfs data this flaw depends on is not present in those versions.
Because the fix is deferred, a residual risk remains: a local user who can access a dangling per-link debugfs entry left behind after a failed Wi-Fi link update on an MLO-capable driver could crash the kernel and cause denial of service. Exploitability is limited, since triggering the flaw requires local access, a runtime driver failure during a link update, and read access to the Wi-Fi debugfs files, which is typically restricted to privileged users, and the demonstrated impact is a system crash rather than loss of confidentiality or integrity.
The upstream CVE record rates this flaw Important (CVSS 3.1 score 7.8), while Red Hat rates it Moderate (CVSS 3.1 score 5.5). Red Hat's lower rating reflects that exploitation requires local access, depends on a rare error path in MLO-capable Wi-Fi drivers, and results in denial of service with no established confidentiality or integrity impact.
Mitigation
Mitigation for this issue is either not available or the currently available options do not 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).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | 7.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | High |
| Integrity Impact | None | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/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)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.