<?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://db.gcve.eu</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>Thu, 19 Nov 2026 23:39:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99218 — coredump: hold RCU while releasing parked threads</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99218</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;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;&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;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://db.gcve.eu/vuln/cve-2026-99218</guid>
    </item>
    <item>
      <title>USN-9165-1 — linux vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-9165-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.10: linux&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - Cryptographic API;
  - File systems infrastructure;
  - Key management;
  - Key Management;
  - io_uring subsystem;
  - PID namespace;
  - Tracing infrastructure;
(CVE-2026-99218, CVE-2026-99219, CVE-2026-99220, CVE-2026-99221,
CVE-2026-99222, CVE-2026-99223, CVE-2026-99224, CVE-2026-99225,
CVE-2026-99226, CVE-2026-99227, CVE-2026-99232, CVE-2026-99233,
CVE-2026-99234, CVE-2026-99235, CVE-2026-99236, CVE-2026-99237,
CVE-2026-99238, CVE-2026-99244, CVE-2026-99245)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.10: linux&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - Cryptographic API;
  - File systems infrastructure;
  - Key management;
  - Key Management;
  - io_uring subsystem;
  - PID namespace;
  - Tracing infrastructure;
(CVE-2026-99218, CVE-2026-99219, CVE-2026-99220, CVE-2026-99221,
CVE-2026-99222, CVE-2026-99223, CVE-2026-99224, CVE-2026-99225,
CVE-2026-99226, CVE-2026-99227, CVE-2026-99232, CVE-2026-99233,
CVE-2026-99234, CVE-2026-99235, CVE-2026-99236, CVE-2026-99237,
CVE-2026-99238, CVE-2026-99244, CVE-2026-99245)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-9165-1</guid>
    </item>
  </channel>
</rss>
