<?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>Wed, 30 Sep 2026 23:23:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31689 — EDAC/mc: Fix error path ordering in edac_mc_alloc()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31689</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/mc: Fix error path ordering in edac_mc_alloc()&lt;/p&gt;
&lt;p&gt;When the mci-&amp;gt;pvt_info allocation in edac_mc_alloc() fails, the error path
will call put_device() which will end up calling the device&amp;#39;s release
function.&lt;/p&gt;
&lt;p&gt;However, the init ordering is wrong such that device_initialize() happens
*after* the failed allocation and thus the device itself and the release
function pointer are not initialized yet when they&amp;#39;re called:&lt;/p&gt;
&lt;p&gt;MCE: In-kernel MCE decoding enabled.
  ------------[ cut here ]------------
  kobject: &amp;#39;(null)&amp;#39;: is not initialized, yet kobject_put() is being called.
  WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd
  CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full)
  RIP: 0010:kobject_put
  Call Trace:
   &amp;lt;TASK&amp;gt;
   edac_mc_alloc+0xbe/0xe0 [edac_core]
   amd64_edac_init+0x7a4/0xff0 [amd64_edac]
   ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac]
   do_one_initcall
   ...&lt;/p&gt;
&lt;p&gt;Reorder the calling sequence so that the device is initialized and thus the
release function pointer is properly set before it can be used.&lt;/p&gt;
&lt;p&gt;This was found by Claude while reviewing another EDAC patch.&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/mc: Fix error path ordering in edac_mc_alloc()&lt;/p&gt;
&lt;p&gt;When the mci-&amp;gt;pvt_info allocation in edac_mc_alloc() fails, the error path
will call put_device() which will end up calling the device&amp;#39;s release
function.&lt;/p&gt;
&lt;p&gt;However, the init ordering is wrong such that device_initialize() happens
*after* the failed allocation and thus the device itself and the release
function pointer are not initialized yet when they&amp;#39;re called:&lt;/p&gt;
&lt;p&gt;MCE: In-kernel MCE decoding enabled.
  ------------[ cut here ]------------
  kobject: &amp;#39;(null)&amp;#39;: is not initialized, yet kobject_put() is being called.
  WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd
  CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full)
  RIP: 0010:kobject_put
  Call Trace:
   &amp;lt;TASK&amp;gt;
   edac_mc_alloc+0xbe/0xe0 [edac_core]
   amd64_edac_init+0x7a4/0xff0 [amd64_edac]
   ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac]
   do_one_initcall
   ...&lt;/p&gt;
&lt;p&gt;Reorder the calling sequence so that the device is initialized and thus the
release function pointer is properly set before it can be used.&lt;/p&gt;
&lt;p&gt;This was found by Claude while reviewing another EDAC patch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31689</guid>
    </item>
  </channel>
</rss>
