<?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>Sun, 04 Oct 2026 21:03:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52707 — sched/psi: Fix use-after-free in ep_remove_wait_queue()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-52707</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;sched/psi: Fix use-after-free in ep_remove_wait_queue()&lt;/p&gt;
&lt;p&gt;If a non-root cgroup gets removed when there is a thread that registered
trigger and is polling on a pressure file within the cgroup, the polling
waitqueue gets freed in the following path:&lt;/p&gt;
&lt;p&gt;do_rmdir
   cgroup_rmdir
     kernfs_drain_open_files
       cgroup_file_release
         cgroup_pressure_release
           psi_trigger_destroy&lt;/p&gt;
&lt;p&gt;However, the polling thread still has a reference to the pressure file and
will access the freed waitqueue when the file is closed or upon exit:&lt;/p&gt;
&lt;p&gt;fput
   ep_eventpoll_release
     ep_free
       ep_remove_wait_queue
         remove_wait_queue&lt;/p&gt;
&lt;p&gt;This results in use-after-free as pasted below.&lt;/p&gt;
&lt;p&gt;The fundamental problem here is that cgroup_file_release() (and
consequently waitqueue&amp;#39;s lifetime) is not tied to the file&amp;#39;s real lifetime.
Using wake_up_pollfree() here might be less than ideal, but it is in line
with the comment at commit 42288cb44c4b (&amp;#34;wait: add wake_up_pollfree()&amp;#34;)
since the waitqueue&amp;#39;s lifetime is not tied to file&amp;#39;s one and can be
considered as another special case. While this would be fixable by somehow
making cgroup_file_release() be tied to the fput(), it would require
sizable refactoring at cgroups or higher layer which might be more
justifiable if we identify more cases like this.&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in _raw_spin_lock_irqsave+0x60/0xc0
  Write of size 4 at addr ffff88810e625328 by task a.out/440…&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;sched/psi: Fix use-after-free in ep_remove_wait_queue()&lt;/p&gt;
&lt;p&gt;If a non-root cgroup gets removed when there is a thread that registered
trigger and is polling on a pressure file within the cgroup, the polling
waitqueue gets freed in the following path:&lt;/p&gt;
&lt;p&gt;do_rmdir
   cgroup_rmdir
     kernfs_drain_open_files
       cgroup_file_release
         cgroup_pressure_release
           psi_trigger_destroy&lt;/p&gt;
&lt;p&gt;However, the polling thread still has a reference to the pressure file and
will access the freed waitqueue when the file is closed or upon exit:&lt;/p&gt;
&lt;p&gt;fput
   ep_eventpoll_release
     ep_free
       ep_remove_wait_queue
         remove_wait_queue&lt;/p&gt;
&lt;p&gt;This results in use-after-free as pasted below.&lt;/p&gt;
&lt;p&gt;The fundamental problem here is that cgroup_file_release() (and
consequently waitqueue&amp;#39;s lifetime) is not tied to the file&amp;#39;s real lifetime.
Using wake_up_pollfree() here might be less than ideal, but it is in line
with the comment at commit 42288cb44c4b (&amp;#34;wait: add wake_up_pollfree()&amp;#34;)
since the waitqueue&amp;#39;s lifetime is not tied to file&amp;#39;s one and can be
considered as another special case. While this would be fixable by somehow
making cgroup_file_release() be tied to the fput(), it would require
sizable refactoring at cgroups or higher layer which might be more
justifiable if we identify more cases like this.&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in _raw_spin_lock_irqsave+0x60/0xc0
  Write of size 4 at addr ffff88810e625328 by task a.out/440…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-52707</guid>
    </item>
  </channel>
</rss>
