<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-20T18:52:23.716580+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-99226</id>
    <title>BELL-CVE-2026-99226</title>
    <updated>2026-11-20T18:52:23.735315+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-99226"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1595</id>
    <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>
    <updated>2026-11-20T18:52:23.735389+00:00</updated>
    <content>certfr-2026-avi-1595</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1595"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-399107</id>
    <title>EUVD-2026-399107</title>
    <updated>2026-11-20T18:52:23.735418+00:00</updated>
    <content>EUVD-2026-399107</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-399107"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99226</id>
    <title>fkie_cve-2026-99226</title>
    <updated>2026-11-20T18:52:23.735436+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>keys: Avoid the owner account dereference in named keyring lookup</p>
<p>Named keyring lookup must keep the storage containing the owner UID
alive through the namespace mapping check.  find_keyring_by_name()
reads keyring-&gt;user-&gt;uid under keyring_name_lock, but that lock protects
the keyring's name entry and allocation, not its separate key_user.</p>
<p>A named session-keyring join can overlap a privileged KEYCTL_CHOWN on
another CPU.  If the keyring holds the last reference to its old dynamic
key_user and the ownership transfer succeeds, the following ordering is
possible:</p>
<p>Named join                         Chown
    find_keyring_by_name()              keyctl_chown_key()
      read_lock(keyring_name_lock)       down_write(key-&gt;sem)
      load old keyring-&gt;user
                                         replace key-&gt;user and key-&gt;uid
                                         up_write(key-&gt;sem)
                                         key_put(key)
                                         key_user_put(old user): free
      read old user-&gt;uid
      read_unlock(keyring_name_lock)</p>
<p>Chown neither takes keyring_name_lock nor key_session_mutex, so it can
free the old account between the pointer load and the UID read.  The
lookup then reads freed memory even though the keyring itself is alive.</p>
<p>Use keyring-&gt;uid for the mapping check.  key_alloc() initializes this
inline owner UID and keyctl_chown_key() updates it on chown.
Th…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-99226"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9pjv-mg4c-3j9m</id>
    <title>GHSA-9pjv-mg4c-3j9m</title>
    <updated>2026-11-20T18:52:23.735507+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>keys: Avoid the owner account dereference in named keyring lookup</p>
<p>Named keyring lookup must keep the storage containing the owner UID
alive through the namespace mapping check.  find_keyring_by_name()
reads keyring-&gt;user-&gt;uid under keyring_name_lock, but that lock protects
the keyring's name entry and allocation, not its separate key_user.</p>
<p>A named session-keyring join can overlap a privileged KEYCTL_CHOWN on
another CPU.  If the keyring holds the last reference to its old dynamic
key_user and the ownership transfer succeeds, the following ordering is
possible:</p>
<p>Named join                         Chown
    find_keyring_by_name()              keyctl_chown_key()
      read_lock(keyring_name_lock)       down_write(key-&gt;sem)
      load old keyring-&gt;user
                                         replace key-&gt;user and key-&gt;uid
                                         up_write(key-&gt;sem)
                                         key_put(key)
                                         key_user_put(old user): free
      read old user-&gt;uid
      read_unlock(keyring_name_lock)</p>
<p>Chown neither takes keyring_name_lock nor key_session_mutex, so it can
free the old account between the pointer load and the UID read.  The
lookup then reads freed memory even though the keyring itself is alive.</p>
<p>Use keyring-&gt;uid for the mapping check.  key_alloc() initializes this
inline owner UID and keyctl_chown_key() updates it on chown.
Th…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9pjv-mg4c-3j9m"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99226</id>
    <title>msrc_CVE-2026-99226 — keys: Avoid the owner account dereference in named keyring lookup</title>
    <updated>2026-11-20T18:52:23.735561+00:00</updated>
    <content>msrc_CVE-2026-99226</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-99226"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99226</id>
    <title>UBUNTU-CVE-2026-99226</title>
    <updated>2026-11-20T18:52:23.735586+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>In the Linux kernel, the following vulnerability has been resolved: keys: Avoid the owner account dereference in named keyring lookup Named keyring lookup must keep the storage containing the owner UID alive through the namespace mapping check.  find_keyring_by_name() reads keyring-&gt;user-&gt;uid under keyring_name_lock, but that lock protects the keyring's name entry and allocation, not its separate key_user. A named session-keyring join can overlap a privileged KEYCTL_CHOWN on another CPU.  If the keyring holds the last reference to its old dynamic key_user and the ownership transfer succeeds, the following ordering is possible:     Named join                         Chown     find_keyring_by_name()              keyctl_chown_key()       read_lock(keyring_name_lock)       down_write(key-&gt;sem)       load old keyring-&gt;user                                          replace key-&gt;user and key-&gt;uid                                          up_write(key-&gt;sem)                                          key_put(key)                                          key_user_put(old user): free       read old user-&gt;uid       read_unlock(keyring_name_lock) Chown neither takes keyring_name_lock nor key_session_mutex, so it can free the old account between the pointer load and the UID read.  The lookup then reads freed memory even though the keyring itself is alive. Use keyring-&gt;uid for the mapping check.  key_alloc() initializes this inline owner UID and keyctl_chown_key() updates it on chown. The exis…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99226"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4302</id>
    <title>WID-SEC-W-2026-4302 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
    <updated>2026-11-20T18:52:23.736032+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4302"/>
  </entry>
</feed>
