<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T08:46:47.401792+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-80718</id>
    <title>CVE-2026-80718 — mm/percpu-km: fix bitmap overflow and accounting in pcpu_create_chunk()</title>
    <updated>2026-09-29T08:46:47.413594+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mm/percpu-km: fix bitmap overflow and accounting in pcpu_create_chunk()</p>
<p>In pcpu_create_chunk(), nr_pages is the total contiguous backing
allocation, i.e., nr_units * pcpu_unit_pages, but pcpu_chunk_populated()
uses it to set chunk-&gt;populated, whose size is pcpu_unit_pages, bitmap. 
Since bit N in chunk-&gt;populated means page offset N inside every unit is
backed.  When nr_units &gt; 1, the function writes beyond chunk-&gt;populated. 
Fix it by using chunk-&gt;nr_pages.</p>
<p>It also fixes the global pcpu_nr_empty_pop_pages accounting, since
pcpu_balance_free() only iterates up to chunk-&gt;nr_pages.</p>
<p>Commit a63d4ac4ab609 ("percpu: make percpu-km set chunk-&gt;populated bitmap
properly") introduced the bitmap overflow issue.  Later, commit
b539b87fed37f ("percpu: implmeent pcpu_nr_empty_pop_pages and
chunk-&gt;nr_populated") added pcpu_nr_empty_pop_pages and caused the
accounting issue.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-80718"/>
  </entry>
</feed>
