CVE-2025-68226: smb: client: fix incomplete backport in cfids_invalidation_worker()
In the Linux kernel, the following vulnerability has been resolved:
smb: client: fix incomplete backport in cfids_invalidation_worker()
The previous commit bdb596ceb4b7 ("smb: client: fix potential UAF in
smb2_close_cached_fid()") was an incomplete backport and missed one
kref_put() call in cfids_invalidation_worker() that should have been
converted to close_cached_dir().
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux SMB client left an earlier use-after-free correction incomplete. A system using affected code could suffer memory corruption when interacting with an SMB share, potentially compromising confidentiality, integrity, and availability. The supplied evidence does not establish the exact affected release range.
Executive priority
Treat this as a high-priority kernel update for fleets using SMB, especially endpoints accessing external or untrusted shares. Use vendor advisories to determine scope before emergency action because the provided version data is ambiguous and active exploitation is not established.
Technical view
The backport of commit bdb596ceb4b7 was incomplete: cfids_invalidation_worker() retained a kref_put() call that should have been converted to close_cached_dir(). The referenced kernel commit resolves this lifecycle-handling error. CVSS 3.1 rates it 8.8, with network reachability, low complexity, no privileges, required user interaction, and high impact.
Likely exposure
Exposure is most likely on Linux systems that use the SMB client and contain the incomplete backport without the corrective commit. The bundle mentions commit bdb596ceb4b7 and Linux 6.17.8, but marks entries default-unaffected; it does not provide a reliable affected-version range. Distribution-specific assessment is required.
Exploitation context
The CVSS vector indicates a network-reachable condition requiring user interaction but no attacker privileges. The supplied record is not in KEV and provides no evidence of active exploitation or public weaponization. Absence from KEV does not prove exploitation has never occurred.
Researcher notes
The core issue is reference-lifecycle handling in cfids_invalidation_worker() after an incomplete backport of a prior UAF correction. The bundle supplies a resolving commit but insufficient branch and release mapping. Researchers should compare distribution patches and function history without assuming every Linux 6.17.8 build is affected.
Mitigation direction
Check Linux distribution and kernel vendor advisories for confirmed affected and corrected builds.
Update to a vendor-supported kernel containing the referenced corrective commit.
Prioritize systems that access remote or potentially untrusted SMB shares.
Avoid inventing workarounds; follow vendor guidance if an update cannot be applied promptly.
Validation and detection
Inventory Linux kernel versions and systems using SMB client functionality.
Determine whether each kernel contains the incomplete backport commit.
Confirm the corrective commit or its vendor-equivalent patch is present.
Recheck vendor advisories because the supplied affected-version mapping is incomplete.
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-2025-68226 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.
1CVSS vectors
3Timeline events
0ADP providers
2Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.