CVE-2026-97564

smb: client: reject userspace cifs.idmap descriptions

N/A
Published: September 25, 2026 at 10:21 AM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: reject userspace cifs.idmap descriptions cifs.idmap key descriptions carry authority-bearing fields (owner and group SIDs and uid/gid values in "os:"/"gs:"/"oi:"/"gi:" 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 -> cifs.idmap) that consumes the unvetted description in root context. 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. This mirrors commit 3da1fdf4efbc ("smb: client: reject userspace cifs.spnego descriptions"), which applied the same restriction to cifs.spnego.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.04d79dba0e00749fa40de8ef13a9b85ce57a1603b
Vendor states this is fixed in 17c93bcd17755523c21abb22cbf2a41a6eb0caaf (fixed)
Vendor states this is fixed in 1d3b24b16a0b013792e8f1e3ed060f0b46f537d1 (fixed)
Vendor states this is fixed in 96751028c0d4dec785709ea3eb0ab38a4f2ded96 (fixed)
Vendor states this is fixed in d9d7eeb0cea5b55b82888f443622fd8d4ee064f3 (fixed)
Vendor states this is fixed in e5964064e3fbe6325893408faff08ca33de0e2c3 (fixed)
Vendor states this is fixed in f29c1ec0e7d8c887a91df3f93bb4617c0ac95c6a (fixed)
Vendor states this is fixed in 3.0 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card