Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-31779 is a high-severity Out-of-bounds Read (CWE-125) vulnerability in Linux Linux Kernel. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 34th 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-31779 is a vulnerability in the Linux kernel's iwlwifi driver, specifically within the mvm component's iwl_mvm_nd_match_info_handler() function. It stems from a memcpy operation that assumes the dynamic array notif->matches is at least as large as the number of bytes to be copied, potentially leading to an out-of-bounds read if the packet length is insufficient. This could result in results->matches containing unwanted data. The issue affects systems using the iwlwifi driver for Intel WiFi hardware and was discovered by the Linux Verification Center using SVACE static analysis.
An attacker with adjacent network access (AV:A) can exploit this vulnerability with low complexity (AC:L), no privileges (PR:N), and no user interaction (UI:N). Successful exploitation enables high-impact confidentiality loss (C:H), such as leakage of sensitive data from kernel memory, and high-impact availability disruption (A:H), potentially causing denial of service via crashes, while maintaining unchanged scope (S:U). The CVSS v3.1 base score is 8.1, reflecting its severity in WiFi-enabled environments.
Mitigation is provided through upstream kernel patches available in the Linux stable repository. Key commits, such as 744fabc338e87b95c4d1ff7c95bc8c0f834c6d99, ca0e9491b98ca4c5b44204b0b3dd8062a3b5fba2, dd90880eb5ec5442b37eb2b95688f4a63f4883e3, e67d8c626ace80b0fa2b48c8ec0a46b508c93442, and f6abac936a0dfd31d6c3e49205ec0ee75a8f887f, extend validation checks to ensure the packet length is sufficient before performing the memcpy, preventing the out-of-bounds read. Security practitioners should update to kernels incorporating these fixes.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-26592
Vulnerability Data
In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler() The memcpy function assumes the dynamic array notif->matches is at least as large as the number of bytes to copy. Otherwise,…
more
results->matches may contain unwanted data. To guarantee safety, extend the validation in one of the checks to ensure sufficient packet length. Found by Linux Verification Center (linuxtesting.org) with SVACE.
- 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.
Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.
Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.