Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-23315 is a high-severity Out-of-bounds Read (CWE-125) vulnerability in Linux Kernel. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-23315 is a vulnerability in the Linux kernel's mt76 WiFi driver, specifically within the mt76_connac2_mac_write_txwi_80211() function. It stems from a lack of frame length validation before accessing management frame fields, enabling a possible out-of-bounds (OOB) read, classified under CWE-125. The issue was published on 2026-03-25 and carries a CVSS v3.1 base score of 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H), highlighting high impacts on confidentiality and availability.
A local attacker with low privileges can exploit this vulnerability due to its low attack complexity and lack of required user interaction. By triggering the faulty function, the attacker can achieve high confidentiality impact through unauthorized access to sensitive memory contents and high availability impact via system crashes or denial of service, without affecting integrity.
Mitigation requires applying upstream patches from the Linux kernel stable repositories, as detailed in commits such as 0fb3b94a9431a3800717e5c3b6fa2e1045a15029, 4e10a730d1b511ff49723371ed6d694dd1b2c785, 7ae7b093b7dba9548a3bc4766b9364b97db4732d, 7b692dff8df0ba5feb8df00f27d906d6eb1fe627, and 84419556359bc96d3fe1623d47a64c86542566cc. These fixes introduce frame length checks prior to accessing management fields, including coverage for mgmt->u.action.u.addba_req.capab, to prevent the OOB access.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-15261
Vulnerability Data
In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: Fix possible oob access in mt76_connac2_mac_write_txwi_80211() Check frame length before accessing the mgmt fields in mt76_connac2_mac_write_txwi_80211 in order to avoid a possible oob access. [fix check to also…
more
cover mgmt->u.action.u.addba_req.capab, correct Fixes tag]
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation directly finds out-of-bounds read flaws through static analysis, fuzzing, and dynamic bounds checks.
Secure engineering principles require bounds checking and memory-safe constructs that stop out-of-bounds reads from being introduced.
Process isolation confines the effects of an out-of-bounds read to the compromised process.
Input validation rejects malformed indices or lengths that would otherwise cause reads outside buffer bounds.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.
Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.
Routine patching replaces vulnerable code containing out-of-bounds read flaws.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance includes fuzzing and static analysis that detect out-of-bounds read defects before release.
Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.