Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-safety flaw in the AMD SPI driver. A low SPI speed value can make kernel code read past a stack array boundary. The source rates it high because a local, low-privileged user could potentially affect confidentiality, integrity, and availability on affected kernels.
Executive priority
Treat as a high-priority kernel patching item, especially for shared Linux systems. It is not presented as internet-exploitable in the sources, but kernel memory-safety bugs can have serious impact when local access exists.
Technical view
amd_set_spi_freq() can iterate past amd_spi_freq when speed_hz is below AMD_SPI_MIN_HZ, producing an out-of-bounds stack access. The kernel fix clamps low speed values by stopping at the final array entry. The issue is classified as CWE-129 with CVSS 7.8, local attack vector, low privileges, and no user interaction.
Likely exposure
Exposure is most likely on systems running affected Linux kernel versions identified by the CVE source, especially where the AMD SPI driver code is present. Distribution kernels may backport fixes, so version strings alone are not enough.
Exploitation context
The supplied sources do not report active exploitation, and KEV is false. The CVSS vector requires local access and low privileges. No remote attack path is identified in the provided evidence.
Researcher notes
Evidence is limited to the CVE description, CVSS metadata, affected version data, and stable kernel commits. The vulnerability appears to be a bounds-checking error in frequency selection logic, fixed by clamping low speed values at the final frequency entry.
Mitigation direction
- Apply Linux kernel updates containing the referenced stable fixes.
- Check distribution vendor advisories for backported fixed packages.
- Prioritize affected systems that allow untrusted local users or workloads.
- Restrict local access on vulnerable systems until patched.
- Monitor vendor guidance for additional mitigation details.
Validation and detection
- Inventory Linux kernel versions across servers, endpoints, and appliances.
- Confirm whether installed kernel packages include the referenced fixes.
- Check whether AMD SPI driver code is built or loaded.
- Review distro advisories because fixes may be backported without version changes.
- After updating, verify systems boot and SPI-dependent functions still work.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCVE-2025-40014 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/7f2c746e09a3746bf937bc708129dc8af61d8f19CVE reference, Linux
- https://git.kernel.org/stable/c/76e51db43fe4aaaebcc5ddda67b0807f7c9bdeccCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.