<?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 21:59:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38424 — perf: Fix sample vs do_exit()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38424</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 sample vs do_exit()&lt;/p&gt;
&lt;p&gt;Baisheng Gao reported an ARM64 crash, which Mark decoded as being a
synchronous external abort -- most likely due to trying to access
MMIO in bad ways.&lt;/p&gt;
&lt;p&gt;The crash further shows perf trying to do a user stack sample while in
exit_mmap()&amp;#39;s tlb_finish_mmu() -- i.e. while tearing down the address
space it is trying to access.&lt;/p&gt;
&lt;p&gt;It turns out that we stop perf after we tear down the userspace mm; a
receipie for disaster, since perf likes to access userspace for
various reasons.&lt;/p&gt;
&lt;p&gt;Flip this order by moving up where we stop perf in do_exit().&lt;/p&gt;
&lt;p&gt;Additionally, harden PERF_SAMPLE_CALLCHAIN and PERF_SAMPLE_STACK_USER
to abort when the current task does not have an mm (exit_mm() makes
sure to set current-&amp;gt;mm = NULL; before commencing with the actual
teardown). Such that CPU wide events don&amp;#39;t trip on this same problem.&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 sample vs do_exit()&lt;/p&gt;
&lt;p&gt;Baisheng Gao reported an ARM64 crash, which Mark decoded as being a
synchronous external abort -- most likely due to trying to access
MMIO in bad ways.&lt;/p&gt;
&lt;p&gt;The crash further shows perf trying to do a user stack sample while in
exit_mmap()&amp;#39;s tlb_finish_mmu() -- i.e. while tearing down the address
space it is trying to access.&lt;/p&gt;
&lt;p&gt;It turns out that we stop perf after we tear down the userspace mm; a
receipie for disaster, since perf likes to access userspace for
various reasons.&lt;/p&gt;
&lt;p&gt;Flip this order by moving up where we stop perf in do_exit().&lt;/p&gt;
&lt;p&gt;Additionally, harden PERF_SAMPLE_CALLCHAIN and PERF_SAMPLE_STACK_USER
to abort when the current task does not have an mm (exit_mm() makes
sure to set current-&amp;gt;mm = NULL; before commencing with the actual
teardown). Such that CPU wide events don&amp;#39;t trip on this same problem.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38424</guid>
    </item>
  </channel>
</rss>
