<?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>Mon, 05 Oct 2026 23:34:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80626 — powerpc/perf: fix preempt count underflow in fsl_emb_pmu_del</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80626</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;powerpc/perf: fix preempt count underflow in fsl_emb_pmu_del&lt;/p&gt;
&lt;p&gt;fsl_emb_pmu_del() unconditionally calls put_cpu_var(cpu_hw_events) at
the &amp;#39;out:&amp;#39; label, but only calls the matching get_cpu_var() after the
&amp;#39;i &amp;lt; 0&amp;#39; early-return check. When event-&amp;gt;hw.idx is negative the
function jumps to &amp;#39;out:&amp;#39; without having taken get_cpu_var(), and the
trailing put_cpu_var() then issues an unmatched preempt_enable(),
underflowing preempt_count.&lt;/p&gt;
&lt;p&gt;On a CONFIG_PREEMPT=y kernel preempt_count would underflow and
eventually present as a &amp;#39;scheduling while atomic&amp;#39; BUG.&lt;/p&gt;
&lt;p&gt;Move put_cpu_var() to pair with get_cpu_var() so the percpu access is
correctly bracketed and the &amp;#39;out:&amp;#39; label only handles perf_pmu_enable.&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;powerpc/perf: fix preempt count underflow in fsl_emb_pmu_del&lt;/p&gt;
&lt;p&gt;fsl_emb_pmu_del() unconditionally calls put_cpu_var(cpu_hw_events) at
the &amp;#39;out:&amp;#39; label, but only calls the matching get_cpu_var() after the
&amp;#39;i &amp;lt; 0&amp;#39; early-return check. When event-&amp;gt;hw.idx is negative the
function jumps to &amp;#39;out:&amp;#39; without having taken get_cpu_var(), and the
trailing put_cpu_var() then issues an unmatched preempt_enable(),
underflowing preempt_count.&lt;/p&gt;
&lt;p&gt;On a CONFIG_PREEMPT=y kernel preempt_count would underflow and
eventually present as a &amp;#39;scheduling while atomic&amp;#39; BUG.&lt;/p&gt;
&lt;p&gt;Move put_cpu_var() to pair with get_cpu_var() so the percpu access is
correctly bracketed and the &amp;#39;out:&amp;#39; label only handles perf_pmu_enable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80626</guid>
    </item>
  </channel>
</rss>
