CVE-2026-97595
Description
A flaw was found in the Linux kernel's mac802154 wireless network subsystem. A lack of proper locking and reference counting allows queued incoming frames to reference network interface data after the interface has been deleted, resulting in a use-after-free vulnerability. An attacker could exploit this timing issue by flooding an interface with network frames while it is being removed, leading to a Denial of Service (DoS) via a kernel crash or potential memory corruption.
Statement
mac802154 queues beacon and MAC command frames while retaining raw sdata and skb dev pointers without holding a netdev reference. A queued worker can dereference the interface after teardown has freed its private data, producing a confirmed slab use after free. Concurrent list insertion from RX softirq and deletion by process context workers can also corrupt the shared RX lists. An adjacent attacker may contribute to the trigger by flooding crafted or repeated IEEE 802.15.4 MAC command or beacon frames while the affected interfaces are active or being removed. For the CVSS the PR:N is selected because a radio adjacent sender does not need a local account or privileges on the target. AV:A is used because exploitation requires access to the local IEEE 802.15.4 communication environment rather than general Internet reachability. AC:H reflects the required timing between frame reception, deferred worker execution, and interface teardown or concurrent list access. Impact is at least denial of service through a kernel crash or stalled interface removal. The confirmed UAF and possible list corruption may also permit confidentiality or integrity impact and should be reviewed for potential privilege escalation.
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).
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.3 | N/A | 7.5 |
| Attack Vector | Adjacent Network | N/A | Adjacent Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| 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:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:A/AC:H/PR:N/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
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.