<?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 20:57:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38352 — posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38352</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: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()&lt;/p&gt;
&lt;p&gt;If an exiting non-autoreaping task has already passed exit_notify() and
calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent
or debugger right after unlock_task_sighand().&lt;/p&gt;
&lt;p&gt;If a concurrent posix_cpu_timer_del() runs at that moment, it won&amp;#39;t be
able to detect timer-&amp;gt;it.cpu.firing != 0: cpu_timer_task_rcu() and/or
lock_task_sighand() will fail.&lt;/p&gt;
&lt;p&gt;Add the tsk-&amp;gt;exit_state check into run_posix_cpu_timers() to fix this.&lt;/p&gt;
&lt;p&gt;This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because
exit_task_work() is called before exit_notify(). But the check still
makes sense, task_work_add(&amp;amp;tsk-&amp;gt;posix_cputimers_work.work) will fail
anyway in this case.&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: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()&lt;/p&gt;
&lt;p&gt;If an exiting non-autoreaping task has already passed exit_notify() and
calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent
or debugger right after unlock_task_sighand().&lt;/p&gt;
&lt;p&gt;If a concurrent posix_cpu_timer_del() runs at that moment, it won&amp;#39;t be
able to detect timer-&amp;gt;it.cpu.firing != 0: cpu_timer_task_rcu() and/or
lock_task_sighand() will fail.&lt;/p&gt;
&lt;p&gt;Add the tsk-&amp;gt;exit_state check into run_posix_cpu_timers() to fix this.&lt;/p&gt;
&lt;p&gt;This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because
exit_task_work() is called before exit_notify(). But the check still
makes sense, task_work_add(&amp;amp;tsk-&amp;gt;posix_cputimers_work.work) will fail
anyway in this case.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38352</guid>
    </item>
  </channel>
</rss>
