<?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:55 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99225</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99225</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-99225</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-399106</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-399106</link>
      <description>EUVD-2026-399106</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-399106</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99225</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99225</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;keys: Check the authorization payload in process keyring searches&lt;/p&gt;
&lt;p&gt;An authorization payload and its saved credentials must remain valid
while search_process_keyrings_rcu() searches the requestor&amp;#39;s keyrings.
The function validates the authorization key, then separately loads
payload.data[0] and unconditionally reads rka-&amp;gt;cred. Validation does
not prevent request_key_auth_revoke() from clearing the payload.&lt;/p&gt;
&lt;p&gt;A request-key helper can assume authority and fork a descendant that
inherits the authorization key. If the descendant misses in its own
keyrings, it falls back to the saved requestor credentials. Successful
target instantiation invalidates the authorization key without clearing
the payload. After the helper exits, UMH_WAIT_PROC returns to the
requester, which calls complete_request_key() and revokes that key.&lt;/p&gt;
&lt;p&gt;With the descendant paused after validation, the paths can interleave
as follows:&lt;/p&gt;
&lt;p&gt;1. The descendant enters search_process_keyrings_rcu() under RCU and
     key_validate() succeeds.
  2. The helper instantiates the target, invalidates the authorization
     key, and exits.
  3. The requester resumes from UMH_WAIT_PROC, calls
     complete_request_key(), and revokes the authorization key.
     request_key_auth_revoke() sets its payload pointer to NULL.
  4. The descendant loads NULL and dereferences rka-&amp;gt;cred.&lt;/p&gt;
&lt;p&gt;This NULL dereference can oops the kernel. RCU delays payload disposal
but does not pre…&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: Check the authorization payload in process keyring searches&lt;/p&gt;
&lt;p&gt;An authorization payload and its saved credentials must remain valid
while search_process_keyrings_rcu() searches the requestor&amp;#39;s keyrings.
The function validates the authorization key, then separately loads
payload.data[0] and unconditionally reads rka-&amp;gt;cred. Validation does
not prevent request_key_auth_revoke() from clearing the payload.&lt;/p&gt;
&lt;p&gt;A request-key helper can assume authority and fork a descendant that
inherits the authorization key. If the descendant misses in its own
keyrings, it falls back to the saved requestor credentials. Successful
target instantiation invalidates the authorization key without clearing
the payload. After the helper exits, UMH_WAIT_PROC returns to the
requester, which calls complete_request_key() and revokes that key.&lt;/p&gt;
&lt;p&gt;With the descendant paused after validation, the paths can interleave
as follows:&lt;/p&gt;
&lt;p&gt;1. The descendant enters search_process_keyrings_rcu() under RCU and
     key_validate() succeeds.
  2. The helper instantiates the target, invalidates the authorization
     key, and exits.
  3. The requester resumes from UMH_WAIT_PROC, calls
     complete_request_key(), and revokes the authorization key.
     request_key_auth_revoke() sets its payload pointer to NULL.
  4. The descendant loads NULL and dereferences rka-&amp;gt;cred.&lt;/p&gt;
&lt;p&gt;This NULL dereference can oops the kernel. RCU delays payload disposal
but does not pre…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-99225</guid>
    </item>
    <item>
      <title>GHSA-fm9c-q6vv-f7qq</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fm9c-q6vv-f7qq</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;keys: Check the authorization payload in process keyring searches&lt;/p&gt;
&lt;p&gt;An authorization payload and its saved credentials must remain valid
while search_process_keyrings_rcu() searches the requestor&amp;#39;s keyrings.
The function validates the authorization key, then separately loads
payload.data[0] and unconditionally reads rka-&amp;gt;cred. Validation does
not prevent request_key_auth_revoke() from clearing the payload.&lt;/p&gt;
&lt;p&gt;A request-key helper can assume authority and fork a descendant that
inherits the authorization key. If the descendant misses in its own
keyrings, it falls back to the saved requestor credentials. Successful
target instantiation invalidates the authorization key without clearing
the payload. After the helper exits, UMH_WAIT_PROC returns to the
requester, which calls complete_request_key() and revokes that key.&lt;/p&gt;
&lt;p&gt;With the descendant paused after validation, the paths can interleave
as follows:&lt;/p&gt;
&lt;p&gt;1. The descendant enters search_process_keyrings_rcu() under RCU and
     key_validate() succeeds.
  2. The helper instantiates the target, invalidates the authorization
     key, and exits.
  3. The requester resumes from UMH_WAIT_PROC, calls
     complete_request_key(), and revokes the authorization key.
     request_key_auth_revoke() sets its payload pointer to NULL.
  4. The descendant loads NULL and dereferences rka-&amp;gt;cred.&lt;/p&gt;
&lt;p&gt;This NULL dereference can oops the kernel. RCU delays payload disposal
but does not pre…&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: Check the authorization payload in process keyring searches&lt;/p&gt;
&lt;p&gt;An authorization payload and its saved credentials must remain valid
while search_process_keyrings_rcu() searches the requestor&amp;#39;s keyrings.
The function validates the authorization key, then separately loads
payload.data[0] and unconditionally reads rka-&amp;gt;cred. Validation does
not prevent request_key_auth_revoke() from clearing the payload.&lt;/p&gt;
&lt;p&gt;A request-key helper can assume authority and fork a descendant that
inherits the authorization key. If the descendant misses in its own
keyrings, it falls back to the saved requestor credentials. Successful
target instantiation invalidates the authorization key without clearing
the payload. After the helper exits, UMH_WAIT_PROC returns to the
requester, which calls complete_request_key() and revokes that key.&lt;/p&gt;
&lt;p&gt;With the descendant paused after validation, the paths can interleave
as follows:&lt;/p&gt;
&lt;p&gt;1. The descendant enters search_process_keyrings_rcu() under RCU and
     key_validate() succeeds.
  2. The helper instantiates the target, invalidates the authorization
     key, and exits.
  3. The requester resumes from UMH_WAIT_PROC, calls
     complete_request_key(), and revokes the authorization key.
     request_key_auth_revoke() sets its payload pointer to NULL.
  4. The descendant loads NULL and dereferences rka-&amp;gt;cred.&lt;/p&gt;
&lt;p&gt;This NULL dereference can oops the kernel. RCU delays payload disposal
but does not pre…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fm9c-q6vv-f7qq</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99225 — keys: Check the authorization payload in process keyring searches</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99225</link>
      <description>msrc_CVE-2026-99225</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-99225</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99225</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99225</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 230 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: keys: Check the authorization payload in process keyring searches An authorization payload and its saved credentials must remain valid while search_process_keyrings_rcu() searches the requestor&amp;#39;s keyrings. The function validates the authorization key, then separately loads payload.data[0] and unconditionally reads rka-&amp;gt;cred. Validation does not prevent request_key_auth_revoke() from clearing the payload. A request-key helper can assume authority and fork a descendant that inherits the authorization key. If the descendant misses in its own keyrings, it falls back to the saved requestor credentials. Successful target instantiation invalidates the authorization key without clearing the payload. After the helper exits, UMH_WAIT_PROC returns to the requester, which calls complete_request_key() and revokes that key. With the descendant paused after validation, the paths can interleave as follows:   1. The descendant enters search_process_keyrings_rcu() under RCU and      key_validate() succeeds.   2. The helper instantiates the target, invalidates the authorization      key, and exits.   3. The requester resumes from UMH_WAIT_PROC, calls      complete_request_key(), and revokes the authorization key.      request_key_auth_revoke() sets its payload pointer to NULL.   4. The descendant loads NULL and dereferences rka-&amp;gt;cred. This NULL dereference can oops the kernel. RCU delays payload disposal but does not prevent t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 230 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: keys: Check the authorization payload in process keyring searches An authorization payload and its saved credentials must remain valid while search_process_keyrings_rcu() searches the requestor&amp;#39;s keyrings. The function validates the authorization key, then separately loads payload.data[0] and unconditionally reads rka-&amp;gt;cred. Validation does not prevent request_key_auth_revoke() from clearing the payload. A request-key helper can assume authority and fork a descendant that inherits the authorization key. If the descendant misses in its own keyrings, it falls back to the saved requestor credentials. Successful target instantiation invalidates the authorization key without clearing the payload. After the helper exits, UMH_WAIT_PROC returns to the requester, which calls complete_request_key() and revokes that key. With the descendant paused after validation, the paths can interleave as follows:   1. The descendant enters search_process_keyrings_rcu() under RCU and      key_validate() succeeds.   2. The helper instantiates the target, invalidates the authorization      key, and exits.   3. The requester resumes from UMH_WAIT_PROC, calls      complete_request_key(), and revokes the authorization key.      request_key_auth_revoke() sets its payload pointer to NULL.   4. The descendant loads NULL and dereferences rka-&amp;gt;cred. This NULL dereference can oops the kernel. RCU delays payload disposal but does not prevent t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99225</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>
