<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 23:47:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97564 — smb: client: reject userspace cifs.idmap descriptions</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-97564</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;smb: client: reject userspace cifs.idmap descriptions&lt;/p&gt;
&lt;p&gt;cifs.idmap key descriptions carry authority-bearing fields (owner and
group SIDs and uid/gid values in &amp;#34;os:&amp;#34;/&amp;#34;gs:&amp;#34;/&amp;#34;oi:&amp;#34;/&amp;#34;gi:&amp;#34; form) that the
cifs.idmap upcall helper treats as kernel-originating inputs.  Unlike
its sibling cifs.spnego, the cifs.idmap key type has no vet_description
hook, so userspace can create keys of this type through
request_key(2)/add_key(2) and supply those fields without CIFS origin.
A request_key(2) call with a non-NULL callout then drives a root
usermodehelper upcall (/sbin/request-key -&amp;gt; cifs.idmap) that consumes
the unvetted description in root context.&lt;/p&gt;
&lt;p&gt;Only accept cifs.idmap descriptions while CIFS is using its private
root_cred to request the key.  id_to_sid()/sid_to_id() already run
under override_creds(root_cred), so the kernel-originated path is
unaffected.&lt;/p&gt;
&lt;p&gt;This mirrors commit 3da1fdf4efbc (&amp;#34;smb: client: reject userspace
cifs.spnego descriptions&amp;#34;), which applied the same restriction to
cifs.spnego.&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;smb: client: reject userspace cifs.idmap descriptions&lt;/p&gt;
&lt;p&gt;cifs.idmap key descriptions carry authority-bearing fields (owner and
group SIDs and uid/gid values in &amp;#34;os:&amp;#34;/&amp;#34;gs:&amp;#34;/&amp;#34;oi:&amp;#34;/&amp;#34;gi:&amp;#34; form) that the
cifs.idmap upcall helper treats as kernel-originating inputs.  Unlike
its sibling cifs.spnego, the cifs.idmap key type has no vet_description
hook, so userspace can create keys of this type through
request_key(2)/add_key(2) and supply those fields without CIFS origin.
A request_key(2) call with a non-NULL callout then drives a root
usermodehelper upcall (/sbin/request-key -&amp;gt; cifs.idmap) that consumes
the unvetted description in root context.&lt;/p&gt;
&lt;p&gt;Only accept cifs.idmap descriptions while CIFS is using its private
root_cred to request the key.  id_to_sid()/sid_to_id() already run
under override_creds(root_cred), so the kernel-originated path is
unaffected.&lt;/p&gt;
&lt;p&gt;This mirrors commit 3da1fdf4efbc (&amp;#34;smb: client: reject userspace
cifs.spnego descriptions&amp;#34;), which applied the same restriction to
cifs.spnego.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-97564</guid>
    </item>
  </channel>
</rss>
