<?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:52:21 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99222</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99222</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-99222</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-399103</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-399103</link>
      <description>EUVD-2026-399103</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-399103</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99222</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99222</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;keys: Protect the read method check against type removal&lt;/p&gt;
&lt;p&gt;keyctl_read_key() checks key-&amp;gt;type-&amp;gt;read without holding key-&amp;gt;sem.
A reference keeps the key alive, but does not pin the module containing
its type. A surviving RxRPC key can therefore be read while AF_RXRPC
is being unloaded:&lt;/p&gt;
&lt;p&gt;KEYCTL_READ task                    Module unload and key GC
  ----------------                   ------------------------
  lookup_user_key()
  permission / possession checks
  load key-&amp;gt;type
                                     af_rxrpc_exit()
                                       unregister_key_type()
                                         GC: down_write(key-&amp;gt;sem)
                                         GC: retype to key_type_dead
                                         GC: up_write(key-&amp;gt;sem)
                                       unregister_key_type() returns
                                     free_module()
  read saved type&amp;#39;s read member&lt;/p&gt;
&lt;p&gt;The final access can read freed module storage. The read invocation in
__keyctl_read_key() is already protected by key-&amp;gt;sem, but the earlier
method check is outside that critical section.&lt;/p&gt;
&lt;p&gt;Move the method check into __keyctl_read_key(), after key_validate() and
under its existing read hold on key-&amp;gt;sem. The check and invocation then
use the same protected type for length queries and every read retry.
The GC cannot retype the key until the semaphore is released, and type
unregistr…&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: Protect the read method check against type removal&lt;/p&gt;
&lt;p&gt;keyctl_read_key() checks key-&amp;gt;type-&amp;gt;read without holding key-&amp;gt;sem.
A reference keeps the key alive, but does not pin the module containing
its type. A surviving RxRPC key can therefore be read while AF_RXRPC
is being unloaded:&lt;/p&gt;
&lt;p&gt;KEYCTL_READ task                    Module unload and key GC
  ----------------                   ------------------------
  lookup_user_key()
  permission / possession checks
  load key-&amp;gt;type
                                     af_rxrpc_exit()
                                       unregister_key_type()
                                         GC: down_write(key-&amp;gt;sem)
                                         GC: retype to key_type_dead
                                         GC: up_write(key-&amp;gt;sem)
                                       unregister_key_type() returns
                                     free_module()
  read saved type&amp;#39;s read member&lt;/p&gt;
&lt;p&gt;The final access can read freed module storage. The read invocation in
__keyctl_read_key() is already protected by key-&amp;gt;sem, but the earlier
method check is outside that critical section.&lt;/p&gt;
&lt;p&gt;Move the method check into __keyctl_read_key(), after key_validate() and
under its existing read hold on key-&amp;gt;sem. The check and invocation then
use the same protected type for length queries and every read retry.
The GC cannot retype the key until the semaphore is released, and type
unregistr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-99222</guid>
    </item>
    <item>
      <title>GHSA-j4rg-4w46-639c</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j4rg-4w46-639c</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;keys: Protect the read method check against type removal&lt;/p&gt;
&lt;p&gt;keyctl_read_key() checks key-&amp;gt;type-&amp;gt;read without holding key-&amp;gt;sem.
A reference keeps the key alive, but does not pin the module containing
its type. A surviving RxRPC key can therefore be read while AF_RXRPC
is being unloaded:&lt;/p&gt;
&lt;p&gt;KEYCTL_READ task                    Module unload and key GC
  ----------------                   ------------------------
  lookup_user_key()
  permission / possession checks
  load key-&amp;gt;type
                                     af_rxrpc_exit()
                                       unregister_key_type()
                                         GC: down_write(key-&amp;gt;sem)
                                         GC: retype to key_type_dead
                                         GC: up_write(key-&amp;gt;sem)
                                       unregister_key_type() returns
                                     free_module()
  read saved type&amp;#39;s read member&lt;/p&gt;
&lt;p&gt;The final access can read freed module storage. The read invocation in
__keyctl_read_key() is already protected by key-&amp;gt;sem, but the earlier
method check is outside that critical section.&lt;/p&gt;
&lt;p&gt;Move the method check into __keyctl_read_key(), after key_validate() and
under its existing read hold on key-&amp;gt;sem. The check and invocation then
use the same protected type for length queries and every read retry.
The GC cannot retype the key until the semaphore is released, and type
unregistr…&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: Protect the read method check against type removal&lt;/p&gt;
&lt;p&gt;keyctl_read_key() checks key-&amp;gt;type-&amp;gt;read without holding key-&amp;gt;sem.
A reference keeps the key alive, but does not pin the module containing
its type. A surviving RxRPC key can therefore be read while AF_RXRPC
is being unloaded:&lt;/p&gt;
&lt;p&gt;KEYCTL_READ task                    Module unload and key GC
  ----------------                   ------------------------
  lookup_user_key()
  permission / possession checks
  load key-&amp;gt;type
                                     af_rxrpc_exit()
                                       unregister_key_type()
                                         GC: down_write(key-&amp;gt;sem)
                                         GC: retype to key_type_dead
                                         GC: up_write(key-&amp;gt;sem)
                                       unregister_key_type() returns
                                     free_module()
  read saved type&amp;#39;s read member&lt;/p&gt;
&lt;p&gt;The final access can read freed module storage. The read invocation in
__keyctl_read_key() is already protected by key-&amp;gt;sem, but the earlier
method check is outside that critical section.&lt;/p&gt;
&lt;p&gt;Move the method check into __keyctl_read_key(), after key_validate() and
under its existing read hold on key-&amp;gt;sem. The check and invocation then
use the same protected type for length queries and every read retry.
The GC cannot retype the key until the semaphore is released, and type
unregistr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j4rg-4w46-639c</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99222 — keys: Protect the read method check against type removal</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99222</link>
      <description>msrc_CVE-2026-99222</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-99222</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99222</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99222</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 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: keys: Protect the read method check against type removal keyctl_read_key() checks key-&amp;gt;type-&amp;gt;read without holding key-&amp;gt;sem. A reference keeps the key alive, but does not pin the module containing its type. A surviving RxRPC key can therefore be read while AF_RXRPC is being unloaded:   KEYCTL_READ task                    Module unload and key GC   ----------------                   ------------------------   lookup_user_key()   permission / possession checks   load key-&amp;gt;type                                      af_rxrpc_exit()                                        unregister_key_type()                                          GC: down_write(key-&amp;gt;sem)                                          GC: retype to key_type_dead                                          GC: up_write(key-&amp;gt;sem)                                        unregister_key_type() returns                                      free_module()   read saved type&amp;#39;s read member The final access can read freed module storage. The read invocation in __keyctl_read_key() is already protected by key-&amp;gt;sem, but the earlier method check is outside that critical section. Move the method check into __keyctl_read_key(), after key_validate() and under its existing read hold on key-&amp;gt;sem. The check and invocation then use the same protected type for length queries and every read retry. The GC cannot retype the key until the semaphore is released, and type unregistration…&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 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: keys: Protect the read method check against type removal keyctl_read_key() checks key-&amp;gt;type-&amp;gt;read without holding key-&amp;gt;sem. A reference keeps the key alive, but does not pin the module containing its type. A surviving RxRPC key can therefore be read while AF_RXRPC is being unloaded:   KEYCTL_READ task                    Module unload and key GC   ----------------                   ------------------------   lookup_user_key()   permission / possession checks   load key-&amp;gt;type                                      af_rxrpc_exit()                                        unregister_key_type()                                          GC: down_write(key-&amp;gt;sem)                                          GC: retype to key_type_dead                                          GC: up_write(key-&amp;gt;sem)                                        unregister_key_type() returns                                      free_module()   read saved type&amp;#39;s read member The final access can read freed module storage. The read invocation in __keyctl_read_key() is already protected by key-&amp;gt;sem, but the earlier method check is outside that critical section. Move the method check into __keyctl_read_key(), after key_validate() and under its existing read hold on key-&amp;gt;sem. The check and invocation then use the same protected type for length queries and every read retry. The GC cannot retype the key until the semaphore is released, and type unregistration…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99222</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>
