← CVE Intelligence

CVE-2025-21991

x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes PUBLISHED

Description (CNA)

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. ]

Affected (CNA)

Vendor / productVersions
Linux / Linuxaffected 979e197968a1e8f09bf0d706801dba4432f85ab3 before d509c4731090ebd9bbdb72c70a2d70003ae81f4f; affected 44a44b57e88f311c1415be1f567c50050913c149 before 985a536e04bbfffb1770df43c6470f635a6b1073; affected be2710deaed3ab1402379a2ede30a3754fe6767a before 18b5d857c6496b78ead2fd10001b81ae32d30cac; affected d576547f489c935b9897d4acf8beee3325dea8a5 before ec52240622c4d218d0240079b7c1d3ec2328a9f4; affected 7ff6edf4fef38ab404ee7861f257e28eaaeed35f before e686349cc19e800dac8971929089ba5ff59abfb0; affected 7ff6edf4fef38ab404ee7861f257e28eaaeed35f before 488ffc0cac38f203979f83634236ee53251ce593; affected 7ff6edf4fef38ab404ee7861f257e28eaaeed35f before 5ac295dfccb5b015493f86694fa13a0dde4d3665; affected 7ff6edf4fef38ab404ee7861f257e28eaaeed35f before e3e89178a9f4a80092578af3ff3c8478f9187d59; affected d6353e2fc12c5b8f00f86efa30ed73d2da2f77be; affected 1b1e0eb1d2971a686b9f7bdc146115bcefcbb960; affected eaf5dea1eb8c2928554b3ca717575cbe232b843c; affected 5.4.235 before 5.4.292; affected 5.10.173 before 5.10.236; affected 5.15.99 before 5.15.180; affected 6.1.16 before 6.1.132; affected 4.14.308 before 4.15; affected 4.19.276 before 4.20; affected 6.2.3 before 6.3
Linux / Linuxaffected 6.3; unaffected 0 before 6.3; unaffected 5.4.292 through 5.4.*; unaffected 5.10.236 through 5.10.*; unaffected 5.15.180 through 5.15.*; unaffected 6.1.132 through 6.1.*; unaffected 6.6.84 through 6.6.*; unaffected 6.12.20 through 6.12.*; unaffected 6.13.8 through 6.13.*; unaffected 6.14 through *

CWE

No CWE identifiers supplied.

References

ADP enrichment

CISA-ADP

No English description supplied.

No references supplied.

CVE

No English description supplied.