<?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>Tue, 17 Nov 2026 10:10:19 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99040</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99040</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-99040</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1537 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</link>
      <description>certfr-2026-avi-1537</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</guid>
    </item>
    <item>
      <title>EUVD-2026-396142</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396142</link>
      <description>EUVD-2026-396142</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396142</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99040</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99040</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KEYS: Fix add_key() race with keyring restriction&lt;/p&gt;
&lt;p&gt;__key_create_or_update() snapshots keyring-&amp;gt;restrict_link before taking
the destination keyring&amp;#39;s semaphore.  keyring_restrict() installs a
restriction while holding that semaphore.&lt;/p&gt;
&lt;p&gt;This allows a writer to observe no restriction, wait for the keyring
owner to install a reject-all restriction and return successfully, and
then link a key using the stale NULL snapshot.  The writer only needs
write permission on the destination keyring.&lt;/p&gt;
&lt;p&gt;Move the restrict_link read after __key_link_lock() and
__key_link_begin().  The read and the subsequent restriction check are
then serialized with restriction installation by keyring-&amp;gt;sem.&lt;/p&gt;
&lt;p&gt;The race was reproduced on v7.2.8 in 19 executions where restriction
installation returned before the link completed.  All 19 linked the key
despite the reject-all restriction.  With this change, 312 executions
reached the same ordering and every add_key() call failed with -EPERM.&lt;/p&gt;
&lt;p&gt;The issue was found by manual concurrency analysis assisted by AI-based
analysis and independently verified with a QEMU reproducer and kernel
instrumentation.&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;KEYS: Fix add_key() race with keyring restriction&lt;/p&gt;
&lt;p&gt;__key_create_or_update() snapshots keyring-&amp;gt;restrict_link before taking
the destination keyring&amp;#39;s semaphore.  keyring_restrict() installs a
restriction while holding that semaphore.&lt;/p&gt;
&lt;p&gt;This allows a writer to observe no restriction, wait for the keyring
owner to install a reject-all restriction and return successfully, and
then link a key using the stale NULL snapshot.  The writer only needs
write permission on the destination keyring.&lt;/p&gt;
&lt;p&gt;Move the restrict_link read after __key_link_lock() and
__key_link_begin().  The read and the subsequent restriction check are
then serialized with restriction installation by keyring-&amp;gt;sem.&lt;/p&gt;
&lt;p&gt;The race was reproduced on v7.2.8 in 19 executions where restriction
installation returned before the link completed.  All 19 linked the key
despite the reject-all restriction.  With this change, 312 executions
reached the same ordering and every add_key() call failed with -EPERM.&lt;/p&gt;
&lt;p&gt;The issue was found by manual concurrency analysis assisted by AI-based
analysis and independently verified with a QEMU reproducer and kernel
instrumentation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-99040</guid>
    </item>
    <item>
      <title>GHSA-xfxp-jqfr-m4g5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xfxp-jqfr-m4g5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KEYS: Fix add_key() race with keyring restriction&lt;/p&gt;
&lt;p&gt;__key_create_or_update() snapshots keyring-&amp;gt;restrict_link before taking
the destination keyring&amp;#39;s semaphore.  keyring_restrict() installs a
restriction while holding that semaphore.&lt;/p&gt;
&lt;p&gt;This allows a writer to observe no restriction, wait for the keyring
owner to install a reject-all restriction and return successfully, and
then link a key using the stale NULL snapshot.  The writer only needs
write permission on the destination keyring.&lt;/p&gt;
&lt;p&gt;Move the restrict_link read after __key_link_lock() and
__key_link_begin().  The read and the subsequent restriction check are
then serialized with restriction installation by keyring-&amp;gt;sem.&lt;/p&gt;
&lt;p&gt;The race was reproduced on v7.2.8 in 19 executions where restriction
installation returned before the link completed.  All 19 linked the key
despite the reject-all restriction.  With this change, 312 executions
reached the same ordering and every add_key() call failed with -EPERM.&lt;/p&gt;
&lt;p&gt;The issue was found by manual concurrency analysis assisted by AI-based
analysis and independently verified with a QEMU reproducer and kernel
instrumentation.&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;KEYS: Fix add_key() race with keyring restriction&lt;/p&gt;
&lt;p&gt;__key_create_or_update() snapshots keyring-&amp;gt;restrict_link before taking
the destination keyring&amp;#39;s semaphore.  keyring_restrict() installs a
restriction while holding that semaphore.&lt;/p&gt;
&lt;p&gt;This allows a writer to observe no restriction, wait for the keyring
owner to install a reject-all restriction and return successfully, and
then link a key using the stale NULL snapshot.  The writer only needs
write permission on the destination keyring.&lt;/p&gt;
&lt;p&gt;Move the restrict_link read after __key_link_lock() and
__key_link_begin().  The read and the subsequent restriction check are
then serialized with restriction installation by keyring-&amp;gt;sem.&lt;/p&gt;
&lt;p&gt;The race was reproduced on v7.2.8 in 19 executions where restriction
installation returned before the link completed.  All 19 linked the key
despite the reject-all restriction.  With this change, 312 executions
reached the same ordering and every add_key() call failed with -EPERM.&lt;/p&gt;
&lt;p&gt;The issue was found by manual concurrency analysis assisted by AI-based
analysis and independently verified with a QEMU reproducer and kernel
instrumentation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xfxp-jqfr-m4g5</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99040 — KEYS: Fix add_key() race with keyring restriction</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99040</link>
      <description>msrc_CVE-2026-99040</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-99040</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99040</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99040</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 249 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KEYS: Fix add_key() race with keyring restriction __key_create_or_update() snapshots keyring-&amp;gt;restrict_link before taking the destination keyring&amp;#39;s semaphore.  keyring_restrict() installs a restriction while holding that semaphore. This allows a writer to observe no restriction, wait for the keyring owner to install a reject-all restriction and return successfully, and then link a key using the stale NULL snapshot.  The writer only needs write permission on the destination keyring. Move the restrict_link read after __key_link_lock() and __key_link_begin().  The read and the subsequent restriction check are then serialized with restriction installation by keyring-&amp;gt;sem. The race was reproduced on v7.2.8 in 19 executions where restriction installation returned before the link completed.  All 19 linked the key despite the reject-all restriction.  With this change, 312 executions reached the same ordering and every add_key() call failed with -EPERM. The issue was found by manual concurrency analysis assisted by AI-based analysis and independently verified with a QEMU reproducer and kernel instrumentation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 249 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KEYS: Fix add_key() race with keyring restriction __key_create_or_update() snapshots keyring-&amp;gt;restrict_link before taking the destination keyring&amp;#39;s semaphore.  keyring_restrict() installs a restriction while holding that semaphore. This allows a writer to observe no restriction, wait for the keyring owner to install a reject-all restriction and return successfully, and then link a key using the stale NULL snapshot.  The writer only needs write permission on the destination keyring. Move the restrict_link read after __key_link_lock() and __key_link_begin().  The read and the subsequent restriction check are then serialized with restriction installation by keyring-&amp;gt;sem. The race was reproduced on v7.2.8 in 19 executions where restriction installation returned before the link completed.  All 19 linked the key despite the reject-all restriction.  With this change, 312 executions reached the same ordering and every add_key() call failed with -EPERM. The issue was found by manual concurrency analysis assisted by AI-based analysis and independently verified with a QEMU reproducer and kernel instrumentation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99040</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&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, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
