<?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 11:37:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93181 — perf/x86/intel/uncore: Fix uncore_box ref/unref ordering</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-93181</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 uncore_box ref/unref ordering&lt;/p&gt;
&lt;p&gt;In uncore_event_cpu_online(), uncore_box_ref() was called before
uncore_change_context().  uncore_box_ref() gates on box-&amp;gt;cpu &amp;gt;= 0,
but box-&amp;gt;cpu is still -1 at that point because uncore_change_context()
has not run yet.  As a result, the box is never initialized on the
first CPU to come online in a die, leaving it permanently
uninitialized in the single-CPU-per-die case.&lt;/p&gt;
&lt;p&gt;Thus, box-&amp;gt;refcnt is one count below the true value, and in the CPU
offline path, the box will be torn down on the second-to-last CPU.&lt;/p&gt;
&lt;p&gt;In uncore_event_cpu_offline(), uncore_box_unref() was called after
uncore_change_context(), so box-&amp;gt;cpu is already -1 when the collector
CPU goes offline, which prevents it from tearing down the box.&lt;/p&gt;
&lt;p&gt;Fix by swapping the call order in both paths so that
uncore_box_{ref,unref}() runs at the point where box-&amp;gt;cpu reflects
the correct context.&lt;/p&gt;
&lt;p&gt;Move allocate_boxes() out of uncore_box_ref() to enable this
reordering.&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 uncore_box ref/unref ordering&lt;/p&gt;
&lt;p&gt;In uncore_event_cpu_online(), uncore_box_ref() was called before
uncore_change_context().  uncore_box_ref() gates on box-&amp;gt;cpu &amp;gt;= 0,
but box-&amp;gt;cpu is still -1 at that point because uncore_change_context()
has not run yet.  As a result, the box is never initialized on the
first CPU to come online in a die, leaving it permanently
uninitialized in the single-CPU-per-die case.&lt;/p&gt;
&lt;p&gt;Thus, box-&amp;gt;refcnt is one count below the true value, and in the CPU
offline path, the box will be torn down on the second-to-last CPU.&lt;/p&gt;
&lt;p&gt;In uncore_event_cpu_offline(), uncore_box_unref() was called after
uncore_change_context(), so box-&amp;gt;cpu is already -1 when the collector
CPU goes offline, which prevents it from tearing down the box.&lt;/p&gt;
&lt;p&gt;Fix by swapping the call order in both paths so that
uncore_box_{ref,unref}() runs at the point where box-&amp;gt;cpu reflects
the correct context.&lt;/p&gt;
&lt;p&gt;Move allocate_boxes() out of uncore_box_ref() to enable this
reordering.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-93181</guid>
    </item>
  </channel>
</rss>
