CVE-2025-21991 Details
Description
In the Linux kernel, the following vulnerability has been resolved: x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes Currently, load_microcode_amd() iterates over all NUMA nodes, retrieves their CPU masks and unconditionally accesses per-CPU data for the first CPU of each mask. According to Documentation/admin-guide/mm/numaperf.rst: "Some memory may share the same node as a CPU, and others are provided as memory only nodes." Therefore, some node CPU masks may be empty and wouldn't have a "first CPU". On a machine with far memory (and therefore CPU-less NUMA nodes): - cpumask_of_node(nid) is 0 - cpumask_first(0) is CONFIG_NR_CPUS - cpu_data(CONFIG_NR_CPUS) accesses the cpu_info per-CPU array at an index that is 1 out of bounds This does not have any security implications since flashing microcode is a privileged operation but I believe this has reliability implications by potentially corrupting memory while flashing a microcode update. When booting with CONFIG_UBSAN_BOUNDS=y on an AMD machine that flashes a microcode update. I get the following splat: UBSAN: array-index-out-of-bounds in arch/x86/kernel/cpu/microcode/amd.c:X:Y index 512 is out of range for type 'unsigned long[512]' [...] Call Trace: dump_stack __ubsan_handle_out_of_bounds load_microcode_amd request_microcode_amd reload_store kernfs_fop_write_iter vfs_write ksys_write do_syscall_64 entry_SYSCALL_64_after_hwframe Change the loop to go over only NUMA nodes which have CPUs before determining whether the first CPU on the respective node needs microcode update. [ bp: Massage commit message, fix typo. ]
A vulnerability in the Linux kernel's handling of microcode updates for AMD processors can lead to an out-of-bounds memory access. This issue arises on systems with CPU-less NUMA nodes, where the first CPU in a node's CPU mask cannot be determined. The flaw occurs in the 'load_microcode_amd' function, which iterates over all NUMA nodes and accesses per-CPU data based on the first CPU of each node. On machines with far memory and CPU-less NUMA nodes, this results in accessing an invalid index in the per-CPU data array, potentially corrupting memory during a microcode update. While this vulnerability does not have security implications, it could disrupt system reliability by mishandling memory during the microcode flashing process.
The vulnerability has been addressed by modifying the microcode loading process to skip NUMA nodes without CPUs, preventing the out-of-bounds access. Users should ensure they are running a version of the Linux kernel that includes this fix.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Oct 1, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-129 | Improper Validation of Array Index | [email protected] |
| CWE-129 | Improper Validation of Array Index | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.14.308, < 4.15 >= 4.19.276, < 4.20 >= 5.4.235, < 5.5 >= 5.10.173, < 5.11 >= 5.15.99, < 5.16 >= 6.1.16, < 6.1.132 >= 6.2.3, < 6.6.84 >= 6.7, < 6.12.20 >= 6.13, < 6.13.8 6.14 rc1 6.14 rc2 6.14 rc3 6.14 rc4 6.14 rc5 6.14 rc6 |
CPE
Remediation
| |
Change History
7 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Nov 3, 2025 | CVE Modified | CVE |
| Oct 1, 2025 | CVE Modified | CISA-ADP |
| Apr 10, 2025 | Initial Analysis | [email protected] |
| Apr 10, 2025 | CVE Modified | kernel.org |
| Apr 2, 2025 | New CVE Received | kernel.org |