CVE-2024-38562: wifi: nl80211: Avoid address calculations via out of bounds array indexing
In the Linux kernel, the following vulnerability has been resolved:
wifi: nl80211: Avoid address calculations via out of bounds array indexing
Before request->channels[] can be used, request->n_channels must be set.
Additionally, address calculations for memory after the "channels" array
need to be calculated from the allocation base ("request") rather than
via the first "out of bounds" index of "channels", otherwise run-time
bounds checking will throw a warning.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel Wi-Fi subsystem flaw that can let a local low-privileged user trigger unsafe memory handling. The CVSS impact is high because successful exploitation could affect confidentiality, integrity, and availability, but the provided sources do not show remote exploitation or active exploitation.
Executive priority
Treat as a high-priority kernel maintenance item, especially for shared Linux systems and endpoints. It is not described as internet-remotely exploitable in the provided sources, but kernel memory issues can have serious business impact if local access is available.
Technical view
CVE-2024-38562 is a CWE-129 out-of-bounds array indexing issue in nl80211. The fix ensures request->n_channels is set before request->channels[] use and avoids deriving post-array addresses from an out-of-bounds index. The vector is local, low complexity, low privilege, no user interaction.
Likely exposure
Systems running affected Linux kernel builds with nl80211 Wi-Fi functionality are the likely exposure. The provided data names Linux kernel versions around 6.6, 6.6.33, 6.8.12, 6.9.3, and 6.10, but distro backports must be checked.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation. The CVSS vector indicates local access with low privileges is required, so this is more urgent on shared systems, endpoints, and devices where untrusted local users can run code.
Researcher notes
Focus validation on nl80211 kernel code provenance and stable commit inclusion, not just upstream version strings. The public description is concise and does not provide exploitability details beyond CVSS, CWE-129, and the memory bounds correction.
Mitigation direction
Apply vendor or distribution kernel updates containing the referenced stable fixes.
Check Linux kernel and distro advisories for exact fixed package versions.
Prioritize shared hosts, laptops, and wireless-capable Linux devices.
Restrict untrusted local shell access where patching is delayed.
Track exceptions for unsupported kernels until upgraded or replaced.
Validation and detection
Inventory Linux kernel versions across managed systems.
Confirm whether distro packages include the referenced stable commits.
Flag affected or uncertain systems for patching review.
Verify patched hosts are running the updated kernel after reboot.
Document distro backport evidence for accepted residual risk.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-129: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-129 · source CWE mapping
Improper Validation of Array Index
Improper Validation of Array Index represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.