<?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>Tue, 29 Sep 2026 06:20:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64048 — net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64048</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;net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot&lt;/p&gt;
&lt;p&gt;On the SMC-D client, slot 0 of ini-&amp;gt;ism_dev[]/ini-&amp;gt;ism_chid[] is
reserved for an SMC-Dv1 device. smc_find_ism_v2_device_clnt()
populates V2 entries starting at index 1, so when no V1 device is
selected slot 0 is left in its kzalloc()&amp;#39;ed state with ism_dev[0] ==
NULL and ism_chid[0] == 0.&lt;/p&gt;
&lt;p&gt;smc_v2_determine_accepted_chid() then matches the peer&amp;#39;s CHID against
the array starting from index 0 using the CHID alone. A malicious
peer replying to a SMC-Dv2-only proposal with d1.chid == 0 matches
the empty slot, ini-&amp;gt;ism_selected becomes 0, and the subsequent
ism_dev[0]-&amp;gt;lgr_lock dereference in smc_conn_create() faults at
offsetof(struct smcd_dev, lgr_lock) == 0x68:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: null-ptr-deref in _raw_spin_lock_bh+0x79/0xe0
  Write of size 4 at addr 0000000000000068 by task exploit/144
  Call Trace:
   _raw_spin_lock_bh
   smc_conn_create (net/smc/smc_core.c:1997)
   __smc_connect (net/smc/af_smc.c:1447)
   smc_connect (net/smc/af_smc.c:1720)
   __sys_connect
   __x64_sys_connect
   do_syscall_64&lt;/p&gt;
&lt;p&gt;Require ism_dev[i] to be non-NULL before accepting a CHID match.&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;net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot&lt;/p&gt;
&lt;p&gt;On the SMC-D client, slot 0 of ini-&amp;gt;ism_dev[]/ini-&amp;gt;ism_chid[] is
reserved for an SMC-Dv1 device. smc_find_ism_v2_device_clnt()
populates V2 entries starting at index 1, so when no V1 device is
selected slot 0 is left in its kzalloc()&amp;#39;ed state with ism_dev[0] ==
NULL and ism_chid[0] == 0.&lt;/p&gt;
&lt;p&gt;smc_v2_determine_accepted_chid() then matches the peer&amp;#39;s CHID against
the array starting from index 0 using the CHID alone. A malicious
peer replying to a SMC-Dv2-only proposal with d1.chid == 0 matches
the empty slot, ini-&amp;gt;ism_selected becomes 0, and the subsequent
ism_dev[0]-&amp;gt;lgr_lock dereference in smc_conn_create() faults at
offsetof(struct smcd_dev, lgr_lock) == 0x68:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: null-ptr-deref in _raw_spin_lock_bh+0x79/0xe0
  Write of size 4 at addr 0000000000000068 by task exploit/144
  Call Trace:
   _raw_spin_lock_bh
   smc_conn_create (net/smc/smc_core.c:1997)
   __smc_connect (net/smc/af_smc.c:1447)
   smc_connect (net/smc/af_smc.c:1720)
   __sys_connect
   __x64_sys_connect
   do_syscall_64&lt;/p&gt;
&lt;p&gt;Require ism_dev[i] to be non-NULL before accepting a CHID match.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64048</guid>
    </item>
  </channel>
</rss>
