CVE-2026-97561: smb: client: honor forceuid/forcegid when mapping SIDs to uid/gid
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 18a72975e9f35aadecc75b031f693f2d1f49308f, 6ac7a29691558bed18e2df1780636b8aa0fd13d5, 89a3b4704af2208e381c55037ff2d1e2365b83e4; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 18a72975e9f35aadecc75b031f693f2d1f49308f, 6ac7a29691558bed18e2df1780636b8aa0fd13d5, 89a3b4704af2208e381c55037ff2d1e2365b83e4; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: smb: client: honor forceuid/forcegid when mapping SIDs to uid/gid When the administrator mounts with forceuid or forcegid (uid=/gid= mount options), they expect all files to appear owned by the specified user/group. However, several code paths unconditionally called sid_to_id() to overwrite cf_uid/cf_gid with server-provided values, ignoring the administrator's explicit override: - smb311_posix_info_to_fattr() (stat via POSIX extensions) - cifs_posix_to_fattr() (readdir via POSIX extensions) - parse_sec_desc() (CIFS ACL ownership mapping) This allowed an untrusted server to dictate local file ownership even when the mount was configured to force specific uid/gid values. Fix all three call sites to check CIFS_MOUNT_OVERR_UID and CIFS_MOUNT_OVERR_GID before calling sid_to_id(), following the same pattern already used by cifs_unix_basic_to_fattr() for unix extensions.
- Published
- Sep 25, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.0affected
- 9409ae58e0759d010b347e7b19ebc90ab5d4b98f and later · before 89a3b4704af2208e381c55037ff2d1e2365b83e4affected · git
- 9409ae58e0759d010b347e7b19ebc90ab5d4b98f and later · before be6eccccec867c22d7c65fab4ea4e91ec3d5b8c6affected · git
- 9409ae58e0759d010b347e7b19ebc90ab5d4b98f and later · before bc35de451c128d399ad185d6269f8847e97cd1c9affected · git
- 9409ae58e0759d010b347e7b19ebc90ab5d4b98f and later · before 6ac7a29691558bed18e2df1780636b8aa0fd13d5affected · git
- 9409ae58e0759d010b347e7b19ebc90ab5d4b98f and later · before e1b74f8f8c1d13190b09fe623b729d36b7ac22a8affected · git
- 9409ae58e0759d010b347e7b19ebc90ab5d4b98f and later · before 18a72975e9f35aadecc75b031f693f2d1f49308faffected · git
- before 3.0not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.2.7-1 | 7.2.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-97559Sep 25, 2026 · smb: client: fail DACL rewrite when the new DACL exceeds 64K0Monitor
- ← EarlierCVE-2026-97560Sep 25, 2026 · smb: client: fix one-byte OOB read in smb2_parse_native_symlink()0Monitor
- Later →CVE-2026-97562Sep 25, 2026 · smb: client: pin DFS superblock in iterator callback30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 18a72975e9f35aadecc75b031f693f2d1f49308f | Vendor (CNA) |
| Linux Linux | 6ac7a29691558bed18e2df1780636b8aa0fd13d5 | Vendor (CNA) |
| Linux Linux | 89a3b4704af2208e381c55037ff2d1e2365b83e4 | Vendor (CNA) |
| Linux Linux | bc35de451c128d399ad185d6269f8847e97cd1c9 | Vendor (CNA) |
| Linux Linux | be6eccccec867c22d7c65fab4ea4e91ec3d5b8c6 | Vendor (CNA) |
| Linux Linux | e1b74f8f8c1d13190b09fe623b729d36b7ac22a8 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.7-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1184 · Sep 28, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/6ac7a29691558bed18e2df1780636b8aa0fd13d5
- git.kernel.org/stable/c/89a3b4704af2208e381c55037ff2d1e2365b83e4
- git.kernel.org/stable/c/bc35de451c128d399ad185d6269f8847e97cd1c9
- git.kernel.org/stable/c/be6eccccec867c22d7c65fab4ea4e91ec3d5b8c6
- git.kernel.org/stable/c/e1b74f8f8c1d13190b09fe623b729d36b7ac22a8
Vendor advisories and official records. Exploit/PoC links are deliberately left out.