CVE-2024-26822: smb: client: set correct id, uid and cruid for multiuser automounts
In the Linux kernel, the following vulnerability has been resolved:
smb: client: set correct id, uid and cruid for multiuser automounts
When uid, gid and cruid are not specified, we need to dynamically
set them into the filesystem context used for automounting otherwise
they'll end up reusing the values from the parent mount.
Security readout for executives and security teams
Plain-English summary
A Linux kernel SMB client bug can apply the wrong user identity values to multiuser automounted SMB shares when uid, gid, and cruid are omitted. The business concern is incorrect identity handling on Linux systems that mount SMB shares. The sources do not provide CVSS, confirmed impact, or active exploitation evidence.
Executive priority
Track this as a targeted Linux infrastructure hygiene item, not an emergency, unless your environment relies heavily on multiuser SMB automounts. Prioritize patching affected file-sharing clients during normal kernel maintenance after confirming vendor applicability.
Technical view
The flaw is in Linux kernel SMB client automount handling. For multiuser automounts, the filesystem context should dynamically set id, uid, and cruid; otherwise automounts can reuse values from the parent mount. Kernel stable commits are referenced as fixes, but the source bundle does not define a CWE or CVSS score.
Likely exposure
Exposure is most likely on Linux systems using the kernel SMB/CIFS client with multiuser automounts, especially configurations omitting uid, gid, and cruid. Downstream distribution exposure depends on kernel packaging and backports, so version strings alone may be insufficient.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation or public weaponization. It describes a resolved kernel behavior issue, not an exploit chain. Treat exploitation status as unconfirmed unless a vendor or CISA source says otherwise.
Researcher notes
Evidence is limited to the CVE record and Linux stable commit references. The likely security relevance is identity or credential-context confusion in SMB multiuser automounts, but the bundle does not state confidentiality, integrity, or privilege impact. Avoid overstating severity without vendor scoring.
Mitigation direction
Check Linux vendor advisories for CVE-2024-26822 and apply the appropriate kernel update.
Prioritize systems using SMB/CIFS multiuser automounts over systems without SMB client mounts.
Review automount configurations that omit uid, gid, or cruid.
Use vendor-supported mitigations if patching is delayed; none are specified in the source bundle.
Validation and detection
Inventory Linux hosts using SMB/CIFS client mounts and automounts.
Identify multiuser automounts where uid, gid, or cruid are not explicitly configured.
Compare deployed kernels with vendor fixed packages or the referenced stable commits.
Confirm no vulnerable kernel packages remain after patch deployment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-26822 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.