<?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-99226 — keys: Avoid the owner account dereference in named keyring lookup</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99226</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;keys: Avoid the owner account dereference in named keyring lookup&lt;/p&gt;
&lt;p&gt;Named keyring lookup must keep the storage containing the owner UID
alive through the namespace mapping check.  find_keyring_by_name()
reads keyring-&amp;gt;user-&amp;gt;uid under keyring_name_lock, but that lock protects
the keyring&amp;#39;s name entry and allocation, not its separate key_user.&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;Named join                         Chown
    find_keyring_by_name()              keyctl_chown_key()
      read_lock(keyring_name_lock)       down_write(key-&amp;gt;sem)
      load old keyring-&amp;gt;user
                                         replace key-&amp;gt;user and key-&amp;gt;uid
                                         up_write(key-&amp;gt;sem)
                                         key_put(key)
                                         key_user_put(old user): free
      read old user-&amp;gt;uid
      read_unlock(keyring_name_lock)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Use keyring-&amp;gt;uid for the mapping check.  key_alloc() initializes this
inline owner UID and keyctl_chown_key() updates it on chown.
Th…&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;keys: Avoid the owner account dereference in named keyring lookup&lt;/p&gt;
&lt;p&gt;Named keyring lookup must keep the storage containing the owner UID
alive through the namespace mapping check.  find_keyring_by_name()
reads keyring-&amp;gt;user-&amp;gt;uid under keyring_name_lock, but that lock protects
the keyring&amp;#39;s name entry and allocation, not its separate key_user.&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;Named join                         Chown
    find_keyring_by_name()              keyctl_chown_key()
      read_lock(keyring_name_lock)       down_write(key-&amp;gt;sem)
      load old keyring-&amp;gt;user
                                         replace key-&amp;gt;user and key-&amp;gt;uid
                                         up_write(key-&amp;gt;sem)
                                         key_put(key)
                                         key_user_put(old user): free
      read old user-&amp;gt;uid
      read_unlock(keyring_name_lock)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Use keyring-&amp;gt;uid for the mapping check.  key_alloc() initializes this
inline owner UID and keyctl_chown_key() updates it on chown.
Th…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99226</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>
