<?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>Sat, 03 Oct 2026 21:38:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23127 — perf: Fix refcount warning on event-&gt;mmap_count increment</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23127</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 refcount warning on event-&amp;gt;mmap_count increment&lt;/p&gt;
&lt;p&gt;When calling refcount_inc(&amp;amp;event-&amp;gt;mmap_count) inside perf_mmap_rb(), the
following warning is triggered:&lt;/p&gt;
&lt;p&gt;refcount_t: addition on 0; use-after-free.
        WARNING: lib/refcount.c:25&lt;/p&gt;
&lt;p&gt;PoC:&lt;/p&gt;
&lt;p&gt;struct perf_event_attr attr = {0};
    int fd = syscall(__NR_perf_event_open, &amp;amp;attr, 0, -1, -1, 0);
    mmap(NULL, 0x3000, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0);
    int victim = syscall(__NR_perf_event_open, &amp;amp;attr, 0, -1, fd,
                         PERF_FLAG_FD_OUTPUT);
    mmap(NULL, 0x3000, PROT_READ | PROT_WRITE, MAP_SHARED, victim, 0);&lt;/p&gt;
&lt;p&gt;This occurs when creating a group member event with the flag
PERF_FLAG_FD_OUTPUT. The group leader should be mmap-ed and then mmap-ing
the event triggers the warning.&lt;/p&gt;
&lt;p&gt;Since the event has copied the output_event in perf_event_set_output(),
event-&amp;gt;rb is set. As a result, perf_mmap_rb() calls
refcount_inc(&amp;amp;event-&amp;gt;mmap_count) when event-&amp;gt;mmap_count = 0.&lt;/p&gt;
&lt;p&gt;Disallow the case when event-&amp;gt;mmap_count = 0. This also prevents two
events from updating the same user_page.&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 refcount warning on event-&amp;gt;mmap_count increment&lt;/p&gt;
&lt;p&gt;When calling refcount_inc(&amp;amp;event-&amp;gt;mmap_count) inside perf_mmap_rb(), the
following warning is triggered:&lt;/p&gt;
&lt;p&gt;refcount_t: addition on 0; use-after-free.
        WARNING: lib/refcount.c:25&lt;/p&gt;
&lt;p&gt;PoC:&lt;/p&gt;
&lt;p&gt;struct perf_event_attr attr = {0};
    int fd = syscall(__NR_perf_event_open, &amp;amp;attr, 0, -1, -1, 0);
    mmap(NULL, 0x3000, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0);
    int victim = syscall(__NR_perf_event_open, &amp;amp;attr, 0, -1, fd,
                         PERF_FLAG_FD_OUTPUT);
    mmap(NULL, 0x3000, PROT_READ | PROT_WRITE, MAP_SHARED, victim, 0);&lt;/p&gt;
&lt;p&gt;This occurs when creating a group member event with the flag
PERF_FLAG_FD_OUTPUT. The group leader should be mmap-ed and then mmap-ing
the event triggers the warning.&lt;/p&gt;
&lt;p&gt;Since the event has copied the output_event in perf_event_set_output(),
event-&amp;gt;rb is set. As a result, perf_mmap_rb() calls
refcount_inc(&amp;amp;event-&amp;gt;mmap_count) when event-&amp;gt;mmap_count = 0.&lt;/p&gt;
&lt;p&gt;Disallow the case when event-&amp;gt;mmap_count = 0. This also prevents two
events from updating the same user_page.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23127</guid>
    </item>
  </channel>
</rss>
