<?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>Fri, 20 Nov 2026 18:43:56 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99218</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99218</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-99218</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1595 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1595</link>
      <description>certfr-2026-avi-1595</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1595</guid>
    </item>
    <item>
      <title>EUVD-2026-399099</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-399099</link>
      <description>EUVD-2026-399099</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-399099</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99218</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99218</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;coredump: hold RCU while releasing parked threads&lt;/p&gt;
&lt;p&gt;coredump_finish() releases the parked threads by clearing -&amp;gt;task in
their core_thread entry and calling wake_up_process() on each of them.
It does that without holding a reference on the task and without being
inside rcu.&lt;/p&gt;
&lt;p&gt;But calling wake_up_process(task) without rcu here isn&amp;#39;t safe. A parked
thread doesn&amp;#39;t need that wakeup to leave. A spurious wakeup or a
preemption after the store is enough for the task to go away.&lt;/p&gt;
&lt;p&gt;So if the coredump client is preempted between the store and
wake_up_process() the thread can exit and be freed in the meantime and
try_to_wake_up() takes pi_lock in freed memory.&lt;/p&gt;
&lt;p&gt;Hold rcu across the loop.&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;coredump: hold RCU while releasing parked threads&lt;/p&gt;
&lt;p&gt;coredump_finish() releases the parked threads by clearing -&amp;gt;task in
their core_thread entry and calling wake_up_process() on each of them.
It does that without holding a reference on the task and without being
inside rcu.&lt;/p&gt;
&lt;p&gt;But calling wake_up_process(task) without rcu here isn&amp;#39;t safe. A parked
thread doesn&amp;#39;t need that wakeup to leave. A spurious wakeup or a
preemption after the store is enough for the task to go away.&lt;/p&gt;
&lt;p&gt;So if the coredump client is preempted between the store and
wake_up_process() the thread can exit and be freed in the meantime and
try_to_wake_up() takes pi_lock in freed memory.&lt;/p&gt;
&lt;p&gt;Hold rcu across the loop.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-99218</guid>
    </item>
    <item>
      <title>GHSA-2cpv-4f6v-pr9h</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2cpv-4f6v-pr9h</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;coredump: hold RCU while releasing parked threads&lt;/p&gt;
&lt;p&gt;coredump_finish() releases the parked threads by clearing -&amp;gt;task in
their core_thread entry and calling wake_up_process() on each of them.
It does that without holding a reference on the task and without being
inside rcu.&lt;/p&gt;
&lt;p&gt;But calling wake_up_process(task) without rcu here isn&amp;#39;t safe. A parked
thread doesn&amp;#39;t need that wakeup to leave. A spurious wakeup or a
preemption after the store is enough for the task to go away.&lt;/p&gt;
&lt;p&gt;So if the coredump client is preempted between the store and
wake_up_process() the thread can exit and be freed in the meantime and
try_to_wake_up() takes pi_lock in freed memory.&lt;/p&gt;
&lt;p&gt;Hold rcu across the loop.&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;coredump: hold RCU while releasing parked threads&lt;/p&gt;
&lt;p&gt;coredump_finish() releases the parked threads by clearing -&amp;gt;task in
their core_thread entry and calling wake_up_process() on each of them.
It does that without holding a reference on the task and without being
inside rcu.&lt;/p&gt;
&lt;p&gt;But calling wake_up_process(task) without rcu here isn&amp;#39;t safe. A parked
thread doesn&amp;#39;t need that wakeup to leave. A spurious wakeup or a
preemption after the store is enough for the task to go away.&lt;/p&gt;
&lt;p&gt;So if the coredump client is preempted between the store and
wake_up_process() the thread can exit and be freed in the meantime and
try_to_wake_up() takes pi_lock in freed memory.&lt;/p&gt;
&lt;p&gt;Hold rcu across the loop.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2cpv-4f6v-pr9h</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99218 — coredump: hold RCU while releasing parked threads</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99218</link>
      <description>msrc_CVE-2026-99218</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-99218</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99218</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99218</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 258 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: coredump: hold RCU while releasing parked threads coredump_finish() releases the parked threads by clearing -&amp;gt;task in their core_thread entry and calling wake_up_process() on each of them. It does that without holding a reference on the task and without being inside rcu. But calling wake_up_process(task) without rcu here isn&amp;#39;t safe. A parked thread doesn&amp;#39;t need that wakeup to leave. A spurious wakeup or a preemption after the store is enough for the task to go away. So if the coredump client is preempted between the store and wake_up_process() the thread can exit and be freed in the meantime and try_to_wake_up() takes pi_lock in freed memory. Hold rcu across the loop.&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 258 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: coredump: hold RCU while releasing parked threads coredump_finish() releases the parked threads by clearing -&amp;gt;task in their core_thread entry and calling wake_up_process() on each of them. It does that without holding a reference on the task and without being inside rcu. But calling wake_up_process(task) without rcu here isn&amp;#39;t safe. A parked thread doesn&amp;#39;t need that wakeup to leave. A spurious wakeup or a preemption after the store is enough for the task to go away. So if the coredump client is preempted between the store and wake_up_process() the thread can exit and be freed in the meantime and try_to_wake_up() takes pi_lock in freed memory. Hold rcu across the loop.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99218</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4302 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4302</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 die Auslösung eines Denial-of-Service-Angriffs, die Manipulation oder Offenlegung von Daten, die Ausführung von beliebigem Code, die Erlangung erweiterter Berechtigungen oder die Umgehung von Sicherheitsmaßnahmen.&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 die Auslösung eines Denial-of-Service-Angriffs, die Manipulation oder Offenlegung von Daten, die Ausführung von beliebigem Code, die Erlangung erweiterter Berechtigungen oder die Umgehung von Sicherheitsmaßnahmen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4302</guid>
    </item>
  </channel>
</rss>
