<?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, 30 Sep 2026 21:12:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31528 — perf: Make sure to use pmu_ctx-&gt;pmu for groups</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31528</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: Make sure to use pmu_ctx-&amp;gt;pmu for groups&lt;/p&gt;
&lt;p&gt;Oliver reported that x86_pmu_del() ended up doing an out-of-bound memory access
when group_sched_in() fails and needs to roll back.&lt;/p&gt;
&lt;p&gt;This *should* be handled by the transaction callbacks, but he found that when
the group leader is a software event, the transaction handlers of the wrong PMU
are used. Despite the move_group case in perf_event_open() and group_sched_in()
using pmu_ctx-&amp;gt;pmu.&lt;/p&gt;
&lt;p&gt;Turns out, inherit uses event-&amp;gt;pmu to clone the events, effectively undoing the
move_group case for all inherited contexts. Fix this by also making inherit use
pmu_ctx-&amp;gt;pmu, ensuring all inherited counters end up in the same pmu context.&lt;/p&gt;
&lt;p&gt;Similarly, __perf_event_read() should use equally use pmu_ctx-&amp;gt;pmu for the
group case.&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: Make sure to use pmu_ctx-&amp;gt;pmu for groups&lt;/p&gt;
&lt;p&gt;Oliver reported that x86_pmu_del() ended up doing an out-of-bound memory access
when group_sched_in() fails and needs to roll back.&lt;/p&gt;
&lt;p&gt;This *should* be handled by the transaction callbacks, but he found that when
the group leader is a software event, the transaction handlers of the wrong PMU
are used. Despite the move_group case in perf_event_open() and group_sched_in()
using pmu_ctx-&amp;gt;pmu.&lt;/p&gt;
&lt;p&gt;Turns out, inherit uses event-&amp;gt;pmu to clone the events, effectively undoing the
move_group case for all inherited contexts. Fix this by also making inherit use
pmu_ctx-&amp;gt;pmu, ensuring all inherited counters end up in the same pmu context.&lt;/p&gt;
&lt;p&gt;Similarly, __perf_event_read() should use equally use pmu_ctx-&amp;gt;pmu for the
group case.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31528</guid>
    </item>
  </channel>
</rss>
