<?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, 07 Oct 2026 17:19:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89442 — platform/x86: ISST: Validate socket ID in clos_assoc ioctl</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89442</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;platform/x86: ISST: Validate socket ID in clos_assoc ioctl&lt;/p&gt;
&lt;p&gt;isst_if_clos_assoc() validates the user-supplied socket_id with
&amp;#39;socket_id &amp;gt; topology_max_packages()&amp;#39;, but isst_common.sst_inst[] is
allocated with topology_max_packages() entries, so the valid index range
is [0, topology_max_packages()).  The &amp;#39;&amp;gt;&amp;#39; comparison lets
socket_id == topology_max_packages() pass and index one entry past the
array.&lt;/p&gt;
&lt;p&gt;In addition, isst_common.sst_inst[socket_id] is NULL for an in-range
package that has no bound TPMI SST instance, and the pointer is used
without a NULL check.  Both the out-of-bounds entry and the NULL pointer
are then dereferenced by map_partition_power_domain_id() and the
following power_domain_info access.&lt;/p&gt;
&lt;p&gt;Reject socket_id &amp;gt;= topology_max_packages() and a NULL sst_inst, matching
the checks already performed by get_instance().&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;platform/x86: ISST: Validate socket ID in clos_assoc ioctl&lt;/p&gt;
&lt;p&gt;isst_if_clos_assoc() validates the user-supplied socket_id with
&amp;#39;socket_id &amp;gt; topology_max_packages()&amp;#39;, but isst_common.sst_inst[] is
allocated with topology_max_packages() entries, so the valid index range
is [0, topology_max_packages()).  The &amp;#39;&amp;gt;&amp;#39; comparison lets
socket_id == topology_max_packages() pass and index one entry past the
array.&lt;/p&gt;
&lt;p&gt;In addition, isst_common.sst_inst[socket_id] is NULL for an in-range
package that has no bound TPMI SST instance, and the pointer is used
without a NULL check.  Both the out-of-bounds entry and the NULL pointer
are then dereferenced by map_partition_power_domain_id() and the
following power_domain_info access.&lt;/p&gt;
&lt;p&gt;Reject socket_id &amp;gt;= topology_max_packages() and a NULL sst_inst, matching
the checks already performed by get_instance().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89442</guid>
    </item>
  </channel>
</rss>
