<?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>Mon, 28 Sep 2026 20:18:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40327 — perf/core: Fix system hang caused by cpu-clock usage</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40327</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: Fix system hang caused by cpu-clock usage&lt;/p&gt;
&lt;p&gt;cpu-clock usage by the async-profiler tool can trigger a system hang,
which got bisected back to the following commit by Octavia Togami:&lt;/p&gt;
&lt;p&gt;18dbcbfabfff (&amp;#34;perf: Fix the POLL_HUP delivery breakage&amp;#34;) causes this issue&lt;/p&gt;
&lt;p&gt;The root cause of the hang is that cpu-clock is a special type of SW
event which relies on hrtimers. The __perf_event_overflow() callback
is invoked from the hrtimer handler for cpu-clock events, and
__perf_event_overflow() tries to call cpu_clock_event_stop()
to stop the event, which calls htimer_cancel() to cancel the hrtimer.&lt;/p&gt;
&lt;p&gt;But that&amp;#39;s a recursion into the hrtimer code from a hrtimer handler,
which (unsurprisingly) deadlocks.&lt;/p&gt;
&lt;p&gt;To fix this bug, use hrtimer_try_to_cancel() instead, and set
the PERF_HES_STOPPED flag, which causes perf_swevent_hrtimer()
to stop the event once it sees the PERF_HES_STOPPED flag.&lt;/p&gt;
&lt;p&gt;[ mingo: Fixed the comments and improved the changelog. ]&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: Fix system hang caused by cpu-clock usage&lt;/p&gt;
&lt;p&gt;cpu-clock usage by the async-profiler tool can trigger a system hang,
which got bisected back to the following commit by Octavia Togami:&lt;/p&gt;
&lt;p&gt;18dbcbfabfff (&amp;#34;perf: Fix the POLL_HUP delivery breakage&amp;#34;) causes this issue&lt;/p&gt;
&lt;p&gt;The root cause of the hang is that cpu-clock is a special type of SW
event which relies on hrtimers. The __perf_event_overflow() callback
is invoked from the hrtimer handler for cpu-clock events, and
__perf_event_overflow() tries to call cpu_clock_event_stop()
to stop the event, which calls htimer_cancel() to cancel the hrtimer.&lt;/p&gt;
&lt;p&gt;But that&amp;#39;s a recursion into the hrtimer code from a hrtimer handler,
which (unsurprisingly) deadlocks.&lt;/p&gt;
&lt;p&gt;To fix this bug, use hrtimer_try_to_cancel() instead, and set
the PERF_HES_STOPPED flag, which causes perf_swevent_hrtimer()
to stop the event once it sees the PERF_HES_STOPPED flag.&lt;/p&gt;
&lt;p&gt;[ mingo: Fixed the comments and improved the changelog. ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40327</guid>
    </item>
  </channel>
</rss>
