<?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://cve.radiocsirt.org</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 23:11:52 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80671</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-80671</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-80671</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>EUVD-2026-367509</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367509</link>
      <description>EUVD-2026-367509</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367509</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80671</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80671</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2026-80671</guid>
    </item>
    <item>
      <title>GHSA-98vx-8r93-84hf</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-98vx-8r93-84hf</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-98vx-8r93-84hf</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80671</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80671</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: perf sched: Fix register_pid() overflow, strcpy, and BUG_ON register_pid() has several issues when processing untrusted perf.data: 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. 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. 3. BUG_ON on allocation failure: perf.data is untrusted input, so    allocation failures should be handled gracefully rather than    killing the process. 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. 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; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: perf sched: Fix register_pid() overflow, strcpy, and BUG_ON register_pid() has several issues when processing untrusted perf.data: 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. 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. 3. BUG_ON on allocation failure: perf.data is untrusted input, so    allocation failures should be handled gracefully rather than    killing the process. 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. 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://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80671</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3075 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</guid>
    </item>
  </channel>
</rss>
