<?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>Thu, 01 Oct 2026 22:36:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23380 — tracing: Fix WARN_ON in tracing_buffers_mmap_close</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23380</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;tracing: Fix WARN_ON in tracing_buffers_mmap_close&lt;/p&gt;
&lt;p&gt;When a process forks, the child process copies the parent&amp;#39;s VMAs but the
user_mapped reference count is not incremented. As a result, when both the
parent and child processes exit, tracing_buffers_mmap_close() is called
twice. On the second call, user_mapped is already 0, causing the function to
return -ENODEV and triggering a WARN_ON.&lt;/p&gt;
&lt;p&gt;Normally, this isn&amp;#39;t an issue as the memory is mapped with VM_DONTCOPY set.
But this is only a hint, and the application can call
madvise(MADVISE_DOFORK) which resets the VM_DONTCOPY flag. When the
application does that, it can trigger this issue on fork.&lt;/p&gt;
&lt;p&gt;Fix it by incrementing the user_mapped reference count without re-mapping
the pages in the VMA&amp;#39;s open callback.&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;tracing: Fix WARN_ON in tracing_buffers_mmap_close&lt;/p&gt;
&lt;p&gt;When a process forks, the child process copies the parent&amp;#39;s VMAs but the
user_mapped reference count is not incremented. As a result, when both the
parent and child processes exit, tracing_buffers_mmap_close() is called
twice. On the second call, user_mapped is already 0, causing the function to
return -ENODEV and triggering a WARN_ON.&lt;/p&gt;
&lt;p&gt;Normally, this isn&amp;#39;t an issue as the memory is mapped with VM_DONTCOPY set.
But this is only a hint, and the application can call
madvise(MADVISE_DOFORK) which resets the VM_DONTCOPY flag. When the
application does that, it can trigger this issue on fork.&lt;/p&gt;
&lt;p&gt;Fix it by incrementing the user_mapped reference count without re-mapping
the pages in the VMA&amp;#39;s open callback.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23380</guid>
    </item>
  </channel>
</rss>
