<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 09:18:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40157 — EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40157</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller&lt;/p&gt;
&lt;p&gt;When loading the i10nm_edac driver on some Intel Granite Rapids servers,
a call trace may appear as follows:&lt;/p&gt;
&lt;p&gt;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]
  ...&lt;/p&gt;
&lt;p&gt;This occurs because some BIOS may disable a memory controller if there
aren&amp;#39;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.&lt;/p&gt;
&lt;p&gt;Fix this call trace by skipping DIMM enumeration on a disabled memory
controller.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller&lt;/p&gt;
&lt;p&gt;When loading the i10nm_edac driver on some Intel Granite Rapids servers,
a call trace may appear as follows:&lt;/p&gt;
&lt;p&gt;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]
  ...&lt;/p&gt;
&lt;p&gt;This occurs because some BIOS may disable a memory controller if there
aren&amp;#39;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.&lt;/p&gt;
&lt;p&gt;Fix this call trace by skipping DIMM enumeration on a disabled memory
controller.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40157</guid>
    </item>
  </channel>
</rss>
