<?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 23:46:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43344 — perf/x86/intel/uncore: Fix die ID init and look up bugs</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43344</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;perf/x86/intel/uncore: Fix die ID init and look up bugs&lt;/p&gt;
&lt;p&gt;In snbep_pci2phy_map_init(), in the nr_node_ids &amp;gt; 8 path,
uncore_device_to_die() may return -1 when all CPUs associated
with the UBOX device are offline.&lt;/p&gt;
&lt;p&gt;Remove the WARN_ON_ONCE(die_id == -1) check for two reasons:&lt;/p&gt;
&lt;p&gt;- The current code breaks out of the loop. This is incorrect because
  pci_get_device() does not guarantee iteration in domain or bus order,
  so additional UBOX devices may be skipped during the scan.&lt;/p&gt;
&lt;p&gt;- Returning -EINVAL is incorrect, since marking offline buses with
  die_id == -1 is expected and should not be treated as an error.&lt;/p&gt;
&lt;p&gt;Separately, when NUMA is disabled on a NUMA-capable platform,
pcibus_to_node() returns NUMA_NO_NODE, causing uncore_device_to_die()
to return -1 for all PCI devices.  As a result,
spr_update_device_location(), used on Intel SPR and EMR, ignores the
corresponding PMON units and does not add them to the RB tree.&lt;/p&gt;
&lt;p&gt;Fix this by using uncore_pcibus_to_dieid(), which retrieves topology
from the UBOX GIDNIDMAP register and works regardless of whether NUMA
is enabled in Linux.  This requires snbep_pci2phy_map_init() to be
added in spr_uncore_pci_init().&lt;/p&gt;
&lt;p&gt;Keep uncore_device_to_die() only for the nr_node_ids &amp;gt; 8 case, where
NUMA is expected to be enabled.&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;perf/x86/intel/uncore: Fix die ID init and look up bugs&lt;/p&gt;
&lt;p&gt;In snbep_pci2phy_map_init(), in the nr_node_ids &amp;gt; 8 path,
uncore_device_to_die() may return -1 when all CPUs associated
with the UBOX device are offline.&lt;/p&gt;
&lt;p&gt;Remove the WARN_ON_ONCE(die_id == -1) check for two reasons:&lt;/p&gt;
&lt;p&gt;- The current code breaks out of the loop. This is incorrect because
  pci_get_device() does not guarantee iteration in domain or bus order,
  so additional UBOX devices may be skipped during the scan.&lt;/p&gt;
&lt;p&gt;- Returning -EINVAL is incorrect, since marking offline buses with
  die_id == -1 is expected and should not be treated as an error.&lt;/p&gt;
&lt;p&gt;Separately, when NUMA is disabled on a NUMA-capable platform,
pcibus_to_node() returns NUMA_NO_NODE, causing uncore_device_to_die()
to return -1 for all PCI devices.  As a result,
spr_update_device_location(), used on Intel SPR and EMR, ignores the
corresponding PMON units and does not add them to the RB tree.&lt;/p&gt;
&lt;p&gt;Fix this by using uncore_pcibus_to_dieid(), which retrieves topology
from the UBOX GIDNIDMAP register and works regardless of whether NUMA
is enabled in Linux.  This requires snbep_pci2phy_map_init() to be
added in spr_uncore_pci_init().&lt;/p&gt;
&lt;p&gt;Keep uncore_device_to_die() only for the nr_node_ids &amp;gt; 8 case, where
NUMA is expected to be enabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43344</guid>
    </item>
  </channel>
</rss>
