Kernel crash via unterminated AMD erratum table
Published May 1, 2025 · Updated Aug 5, 2026
Out-of-bounds read in Linux 6.14 through 6.14.2 and 6.15-rc1 allows local users to crash the kernel during CPU initialization. The erratum_1386_microcode array in arch/x86/kernel/cpu/amd.c lacks its terminating empty entry, so fix_erratum_1386 scans beyond the table into adjacent kernel memory. The path runs only during boot-CPU initialization or secondary-CPU bring-up on affected AMD Zen 1 and Zen 2 systems.
Summary
What happened
Out-of-bounds read in Linux 6.14 through 6.14.2 and 6.15-rc1 allows local users to crash the kernel during CPU initialization. The erratum_1386_microcode array in arch/x86/kernel/cpu/amd.c lacks its terminating empty entry, so fix_erratum_1386 scans beyond the table into adjacent kernel memory. The path runs only during boot-CPU initialization or secondary-CPU bring-up on affected AMD Zen 1 and Zen 2 systems.
The record
- CVE
- CVE-2025-37751
- Published
- May 1, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=f3f3251526739bb975b97f840c56b3054dba8638 <1b518f73f1b6f59e083ec33dea22d9a1a275a970
- Affected versionversion=f3f3251526739bb975b97f840c56b3054dba8638 <f0df00ebc57f803603f2a2e0df197e51f06fbe90
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.
Weakness, pattern, technique
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