linux-cve-announce - CVE-2025-40157: EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025111258-CVE-2025-40157-d08c@gregkh>
Date: Wed, 12 Nov 2025 19:24:33 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40157: EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller

When loading the i10nm_edac driver on some Intel Granite Rapids servers,
a call trace may appear as follows:

  UBSAN: shift-out-of-bounds in drivers/edac/skx_common.c:453:16
  shift exponent -66 is negative
  ...
  __ubsan_handle_shift_out_of_bounds+0x1e3/0x390
  skx_get_dimm_info.cold+0x47/0xd40 [skx_edac_common]
  i10nm_get_dimm_config+0x23e/0x390 [i10nm_edac]
  skx_register_mci+0x159/0x220 [skx_edac_common]
  i10nm_init+0xcb0/0x1ff0 [i10nm_edac]
  ...

This occurs because some BIOS may disable a memory controller if there
aren't any memory DIMMs populated on this memory controller. The DIMMMTR
register of this disabled memory controller contains the invalid value
~0, resulting in the call trace above.

Fix this call trace by skipping DIMM enumeration on a disabled memory
controller.

The Linux kernel CVE team has assigned CVE-2025-40157 to this issue.

Affected and fixed versions
===========================

	Issue introduced in 6.3 with commit ba987eaaabf99b462cdfed86274e3455d5126349 and fixed in 6.6.112 with commit 8100b6c0f9089d5b156642b81270ce27fff17490
	Issue introduced in 6.3 with commit ba987eaaabf99b462cdfed86274e3455d5126349 and fixed in 6.12.53 with commit 1652f14cf3bef5a4baa232de954fc22bdcaa78fe
	Issue introduced in 6.3 with commit ba987eaaabf99b462cdfed86274e3455d5126349 and fixed in 6.17.3 with commit c20da24272f1ac79e9f9083bba577d049cd02bbb
	Issue introduced in 6.3 with commit ba987eaaabf99b462cdfed86274e3455d5126349 and fixed in 6.18-rc1 with commit 2e6fe1bbefd9c059c3787d1c620fe67343a94dff

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-40157
will be updated if fixes are backported, please check that for the most
up to date information about this issue.

Affected files
==============

The file(s) affected by this issue are:
	drivers/edac/i10nm_base.c

Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/8100b6c0f9089d5b156642b81270ce27fff17490
	https://git.kernel.org/stable/c/1652f14cf3bef5a4baa232de954fc22bdcaa78fe
	https://git.kernel.org/stable/c/c20da24272f1ac79e9f9083bba577d049cd02bbb
	https://git.kernel.org/stable/c/2e6fe1bbefd9c059c3787d1c620fe67343a94dff