<?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 15:10:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-48950 — perf: Fix perf_pending_task() UaF</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-48950</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: Fix perf_pending_task() UaF&lt;/p&gt;
&lt;p&gt;Per syzbot it is possible for perf_pending_task() to run after the
event is free()&amp;#39;d. There are two related but distinct cases:&lt;/p&gt;
&lt;p&gt;- the task_work was already queued before destroying the event;
 - destroying the event itself queues the task_work.&lt;/p&gt;
&lt;p&gt;The first cannot be solved using task_work_cancel() since
perf_release() itself might be called from a task_work (____fput),
which means the current-&amp;gt;task_works list is already empty and
task_work_cancel() won&amp;#39;t be able to find the perf_pending_task()
entry.&lt;/p&gt;
&lt;p&gt;The simplest alternative is extending the perf_event lifetime to cover
the task_work.&lt;/p&gt;
&lt;p&gt;The second is just silly, queueing a task_work while you know the
event is going away makes no sense and is easily avoided by
re-arranging how the event is marked STATE_DEAD and ensuring it goes
through STATE_OFF on the way down.&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: Fix perf_pending_task() UaF&lt;/p&gt;
&lt;p&gt;Per syzbot it is possible for perf_pending_task() to run after the
event is free()&amp;#39;d. There are two related but distinct cases:&lt;/p&gt;
&lt;p&gt;- the task_work was already queued before destroying the event;
 - destroying the event itself queues the task_work.&lt;/p&gt;
&lt;p&gt;The first cannot be solved using task_work_cancel() since
perf_release() itself might be called from a task_work (____fput),
which means the current-&amp;gt;task_works list is already empty and
task_work_cancel() won&amp;#39;t be able to find the perf_pending_task()
entry.&lt;/p&gt;
&lt;p&gt;The simplest alternative is extending the perf_event lifetime to cover
the task_work.&lt;/p&gt;
&lt;p&gt;The second is just silly, queueing a task_work while you know the
event is going away makes no sense and is easily avoided by
re-arranging how the event is marked STATE_DEAD and ensuring it goes
through STATE_OFF on the way down.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-48950</guid>
    </item>
  </channel>
</rss>
