Kernel stack access via unchecked SPI speed
Published Apr 18, 2025 · Updated May 11, 2026
Out-of-bounds access in Linux 6.14 and 6.14.1 allows local users to trigger invalid kernel stack access via a low AMD SPI speed. The amd_set_spi_freq function exhausts the amd_spi_freq array when speed_hz is below AMD_SPI_MIN_HZ, then dereferences the out-of-range index. Access requires local low-privileged control of an AMD SPI transfer; public records demonstrate neither a resulting crash nor code execution.
Summary
What happened
Out-of-bounds access in Linux 6.14 and 6.14.1 allows local users to trigger invalid kernel stack access via a low AMD SPI speed. The amd_set_spi_freq function exhausts the amd_spi_freq array when speed_hz is below AMD_SPI_MIN_HZ, then dereferences the out-of-range index. Access requires local low-privileged control of an AMD SPI transfer; public records demonstrate neither a resulting crash nor code execution.
The record
- CVE
- CVE-2025-40014
- Published
- Apr 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-129, CAPEC-100
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.14
- Affected versionversion=e6204f39fe3a7b4538815a2d778b601bd543649e <76e51db43fe4aaaebcc5ddda67b0807f7c9bdecc
- Affected versionversion=e6204f39fe3a7b4538815a2d778b601bd543649e <7f2c746e09a3746bf937bc708129dc8af61d8f19
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo