x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Original 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.
From the CVE record · Linux
References
- git.kernel.org/stable/c/d509c4731090ebd9bbdb72c70a2d70003ae81f4fPatch
- git.kernel.org/stable/c/985a536e04bbfffb1770df43c6470f635a6b1073Patch
- git.kernel.org/stable/c/18b5d857c6496b78ead2fd10001b81ae32d30cacPatch
- git.kernel.org/stable/c/ec52240622c4d218d0240079b7c1d3ec2328a9f4Patch
- git.kernel.org/stable/c/e686349cc19e800dac8971929089ba5ff59abfb0Patch
- git.kernel.org/stable/c/488ffc0cac38f203979f83634236ee53251ce593Patch
- git.kernel.org/stable/c/5ac295dfccb5b015493f86694fa13a0dde4d3665Patch
- git.kernel.org/stable/c/e3e89178a9f4a80092578af3ff3c8478f9187d59Patch
- lists.debian.org/debian-lts-announce/2025/05/msg00045.html
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- github.com/CVEProject/cvelistV5/tree/main/cves/2025/21xxx/CVE-2025-21991.json
- nvd.nist.gov/vuln/detail/CVE-2025-21991