<?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 16:51:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64556 — perf/core: Detach event groups during remove_on_exec</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64556</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: Detach event groups during remove_on_exec&lt;/p&gt;
&lt;p&gt;perf_event_remove_on_exec() removes events by calling
perf_event_exit_event(). For top-level events, this removes the event from
the context with DETACH_EXIT only.&lt;/p&gt;
&lt;p&gt;This can leave inconsistent group state when a removed event is a group
leader and the group contains siblings without remove_on_exec. If the group
was active, the surviving siblings can remain active and attached to the
removed leader&amp;#39;s sibling list, but are no longer represented by a valid
group leader on the PMU context active lists.&lt;/p&gt;
&lt;p&gt;A later close of the removed leader uses DETACH_GROUP and can promote the
still-active siblings from this stale group state. The next schedule-in can
then add an already-linked active_list entry again, corrupting the PMU
context active list.&lt;/p&gt;
&lt;p&gt;With DEBUG_LIST enabled, this is caught as a list_add double-add in
merge_sched_in().&lt;/p&gt;
&lt;p&gt;Fix this by detaching group relationships when remove_on_exec removes an
event. This preserves the existing task-exit and revoke behavior, while
ensuring surviving siblings are ungrouped before the removed event leaves
the context.&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: Detach event groups during remove_on_exec&lt;/p&gt;
&lt;p&gt;perf_event_remove_on_exec() removes events by calling
perf_event_exit_event(). For top-level events, this removes the event from
the context with DETACH_EXIT only.&lt;/p&gt;
&lt;p&gt;This can leave inconsistent group state when a removed event is a group
leader and the group contains siblings without remove_on_exec. If the group
was active, the surviving siblings can remain active and attached to the
removed leader&amp;#39;s sibling list, but are no longer represented by a valid
group leader on the PMU context active lists.&lt;/p&gt;
&lt;p&gt;A later close of the removed leader uses DETACH_GROUP and can promote the
still-active siblings from this stale group state. The next schedule-in can
then add an already-linked active_list entry again, corrupting the PMU
context active list.&lt;/p&gt;
&lt;p&gt;With DEBUG_LIST enabled, this is caught as a list_add double-add in
merge_sched_in().&lt;/p&gt;
&lt;p&gt;Fix this by detaching group relationships when remove_on_exec removes an
event. This preserves the existing task-exit and revoke behavior, while
ensuring surviving siblings are ungrouped before the removed event leaves
the context.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64556</guid>
    </item>
  </channel>
</rss>
