<?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>Wed, 30 Sep 2026 03:40:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80671 — perf sched: Fix register_pid() overflow, strcpy, and BUG_ON</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80671</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 sched: Fix register_pid() overflow, strcpy, and BUG_ON&lt;/p&gt;
&lt;p&gt;register_pid() has several issues when processing untrusted perf.data:&lt;/p&gt;
&lt;p&gt;1. Integer overflow: (pid + 1) * sizeof(struct task_desc *) can wrap
   to a small value on 32-bit systems when pid is large (e.g.
   0x40000000), causing realloc to return a tiny buffer followed by
   out-of-bounds writes in the initialization loop.&lt;/p&gt;
&lt;p&gt;2. Heap buffer overflow: strcpy(task-&amp;gt;comm, comm) copies the
   untrusted comm string into a fixed 20-byte COMM_LEN buffer with
   no length check.&lt;/p&gt;
&lt;p&gt;3. BUG_ON on allocation failure: perf.data is untrusted input, so
   allocation failures should be handled gracefully rather than
   killing the process.&lt;/p&gt;
&lt;p&gt;4. Realloc of sched-&amp;gt;tasks assigned directly back, leaking the old
   pointer on failure; nr_tasks incremented before the realloc,
   leaving corrupted state on failure.&lt;/p&gt;
&lt;p&gt;Cap pid at PID_MAX_LIMIT (4194304, matching the kernel&amp;#39;s maximum
on 64-bit), replace strcpy with strlcpy, guard against NULL comm,
replace BUG_ON with NULL returns using safe realloc patterns, and
add NULL checks in callers that dereference the result.&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 sched: Fix register_pid() overflow, strcpy, and BUG_ON&lt;/p&gt;
&lt;p&gt;register_pid() has several issues when processing untrusted perf.data:&lt;/p&gt;
&lt;p&gt;1. Integer overflow: (pid + 1) * sizeof(struct task_desc *) can wrap
   to a small value on 32-bit systems when pid is large (e.g.
   0x40000000), causing realloc to return a tiny buffer followed by
   out-of-bounds writes in the initialization loop.&lt;/p&gt;
&lt;p&gt;2. Heap buffer overflow: strcpy(task-&amp;gt;comm, comm) copies the
   untrusted comm string into a fixed 20-byte COMM_LEN buffer with
   no length check.&lt;/p&gt;
&lt;p&gt;3. BUG_ON on allocation failure: perf.data is untrusted input, so
   allocation failures should be handled gracefully rather than
   killing the process.&lt;/p&gt;
&lt;p&gt;4. Realloc of sched-&amp;gt;tasks assigned directly back, leaking the old
   pointer on failure; nr_tasks incremented before the realloc,
   leaving corrupted state on failure.&lt;/p&gt;
&lt;p&gt;Cap pid at PID_MAX_LIMIT (4194304, matching the kernel&amp;#39;s maximum
on 64-bit), replace strcpy with strlcpy, guard against NULL comm,
replace BUG_ON with NULL returns using safe realloc patterns, and
add NULL checks in callers that dereference the result.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80671</guid>
    </item>
  </channel>
</rss>
