<?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 05:34:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74637 — perf/core: Fix group leader use-after-free after sibling detach</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74637</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/core: Fix group leader use-after-free after sibling detach&lt;/p&gt;
&lt;p&gt;perf_group_detach() handles leader and sibling detach differently. When the
group leader is detached, all siblings are promoted to singleton events and
their group_leader pointer is reset to themselves. When a sibling is
detached, it is removed from the leader&amp;#39;s sibling_list, but its
group_leader pointer is left pointing at the old leader.&lt;/p&gt;
&lt;p&gt;That is harmless when the sibling is being closed and freed immediately, as
in the DETACH_DEAD path. It is not safe when the sibling is detached but
kept alive, such as during CPU hotplug with DETACH_GROUP. In that case the
sibling is removed from the context, while its file descriptor can still
keep it alive.&lt;/p&gt;
&lt;p&gt;A typical failing sequence is:&lt;/p&gt;
&lt;p&gt;- A group contains leader L and sibling S.
  - CPU hot-unplug detaches S with DETACH_GROUP, removing it from
    L-&amp;gt;sibling_list but leaving S-&amp;gt;group_leader == L.
  - L is later closed and freed.
  - A PERF_IOC_FLAG_GROUP ioctl on S follows S-&amp;gt;group_leader and
    dereferences the freed leader.&lt;/p&gt;
&lt;p&gt;This was reproduced by running the perf event fuzzer, CPU hotplug, and a
stress workload concurrently:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel paging request at virtual address 006b6b6b6b6b6cdb
  CPU: 2 PID: 12489 Comm: perf_fuzzer 6.18.7 PREEMPT
  pc : perf_ioctl+0x34c/0xc68
  x20: ffffff89a3fa2c70 x8 : 6b6b6b6b6b6b6b6b
  Code: 943c4a0e 340047a0 f9404a94 f9411e88 (f940b908)
  Call trace:…&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/core: Fix group leader use-after-free after sibling detach&lt;/p&gt;
&lt;p&gt;perf_group_detach() handles leader and sibling detach differently. When the
group leader is detached, all siblings are promoted to singleton events and
their group_leader pointer is reset to themselves. When a sibling is
detached, it is removed from the leader&amp;#39;s sibling_list, but its
group_leader pointer is left pointing at the old leader.&lt;/p&gt;
&lt;p&gt;That is harmless when the sibling is being closed and freed immediately, as
in the DETACH_DEAD path. It is not safe when the sibling is detached but
kept alive, such as during CPU hotplug with DETACH_GROUP. In that case the
sibling is removed from the context, while its file descriptor can still
keep it alive.&lt;/p&gt;
&lt;p&gt;A typical failing sequence is:&lt;/p&gt;
&lt;p&gt;- A group contains leader L and sibling S.
  - CPU hot-unplug detaches S with DETACH_GROUP, removing it from
    L-&amp;gt;sibling_list but leaving S-&amp;gt;group_leader == L.
  - L is later closed and freed.
  - A PERF_IOC_FLAG_GROUP ioctl on S follows S-&amp;gt;group_leader and
    dereferences the freed leader.&lt;/p&gt;
&lt;p&gt;This was reproduced by running the perf event fuzzer, CPU hotplug, and a
stress workload concurrently:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel paging request at virtual address 006b6b6b6b6b6cdb
  CPU: 2 PID: 12489 Comm: perf_fuzzer 6.18.7 PREEMPT
  pc : perf_ioctl+0x34c/0xc68
  x20: ffffff89a3fa2c70 x8 : 6b6b6b6b6b6b6b6b
  Code: 943c4a0e 340047a0 f9404a94 f9411e88 (f940b908)
  Call trace:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74637</guid>
    </item>
  </channel>
</rss>
