<?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 09:26:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50095 — posix-cpu-timers: Cleanup CPU timers before freeing them during exec</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50095</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;posix-cpu-timers: Cleanup CPU timers before freeing them during exec&lt;/p&gt;
&lt;p&gt;Commit 55e8c8eb2c7b (&amp;#34;posix-cpu-timers: Store a reference to a pid not a
task&amp;#34;) started looking up tasks by PID when deleting a CPU timer.&lt;/p&gt;
&lt;p&gt;When a non-leader thread calls execve, it will switch PIDs with the leader
process. Then, as it calls exit_itimers, posix_cpu_timer_del cannot find
the task because the timer still points out to the old PID.&lt;/p&gt;
&lt;p&gt;That means that armed timers won&amp;#39;t be disarmed, that is, they won&amp;#39;t be
removed from the timerqueue_list. exit_itimers will still release their
memory, and when that list is later processed, it leads to a
use-after-free.&lt;/p&gt;
&lt;p&gt;Clean up the timers from the de-threaded task before freeing them. This
prevents a reported use-after-free.&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;posix-cpu-timers: Cleanup CPU timers before freeing them during exec&lt;/p&gt;
&lt;p&gt;Commit 55e8c8eb2c7b (&amp;#34;posix-cpu-timers: Store a reference to a pid not a
task&amp;#34;) started looking up tasks by PID when deleting a CPU timer.&lt;/p&gt;
&lt;p&gt;When a non-leader thread calls execve, it will switch PIDs with the leader
process. Then, as it calls exit_itimers, posix_cpu_timer_del cannot find
the task because the timer still points out to the old PID.&lt;/p&gt;
&lt;p&gt;That means that armed timers won&amp;#39;t be disarmed, that is, they won&amp;#39;t be
removed from the timerqueue_list. exit_itimers will still release their
memory, and when that list is later processed, it leads to a
use-after-free.&lt;/p&gt;
&lt;p&gt;Clean up the timers from the de-threaded task before freeing them. This
prevents a reported use-after-free.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50095</guid>
    </item>
  </channel>
</rss>
