CVE-2025-68219cifs: fix memory leak in smb3_fs_context_parse_param error path
- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: cifs: fix memory leak in smb3_fs_context_parse_param error path Add proper cleanup of ctx->source and fc->source to the cifs_parse_mount_err error handler. This ensures that memory allocated for the source strings is correctly freed on all error paths, matching the cleanup already performed in the success path by smb3_cleanup_fs_context_contents(). Pointers are also set to NULL after freeing to prevent potential double-free issues. This change fixes a memory leak originally detected by syzbot. The leak occurred when processing Opt_source mount options if an error happened after ctx->source and fc->source were successfully allocated but before the function completed. The specific leak sequence was: 1. ctx->source = smb3_fs_context_fullpath(ctx, '/') allocates memory 2. fc->source = kstrdup(ctx->source, GFP_KERNEL) allocates more memory 3. A subsequent error jumps to cifs_parse_mount_err 4. The old error handler freed passwords but not the source strings, causing the memory to leak. This issue was not addressed by commit e8c73eb7db0a ("cifs: client: fix memory leak in smb3_fs_context_parse_param"), which only fixed leaks from repeated fsconfig() calls but not this error path. Patch updated with minor change suggested by kernel test robot
Timeline
ID reserved
By Linux
Published
- 11 months later
· 11 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 24e0a1eff9e2b9835a6e7c17039dfb6ecfd81f1f – < a8071fd69df335362be5ecf5df5a167fd1eb5853
- affected 24e0a1eff9e2b9835a6e7c17039dfb6ecfd81f1f – < 7627864dc3121f39e220f5253a227edf472de59e
- affected 24e0a1eff9e2b9835a6e7c17039dfb6ecfd81f1f – < 48d69290270891f988e72edddd9688c20515421d
- affected 24e0a1eff9e2b9835a6e7c17039dfb6ecfd81f1f – < 37010021d7e0341bb241ca00bcbae31f2c50b23f
- affected 24e0a1eff9e2b9835a6e7c17039dfb6ecfd81f1f – < 7e4d9120cfa413dd34f4f434befc5dbe6c38b2e5
- affected 5.11
- unaffected < 5.11
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.118 – ≤ 6.6.*
- unaffected 6.12.60 – ≤ 6.12.*
- unaffected 6.17.10 – ≤ 6.17.*
- unaffected 6.18 – ≤ *
References
References5
- https://git.kernel.org/stable/c/a8071fd69df335362be5ecf5df5a167fd1eb5853 (opens in a new tab)
- https://git.kernel.org/stable/c/7627864dc3121f39e220f5253a227edf472de59e (opens in a new tab)
- https://git.kernel.org/stable/c/48d69290270891f988e72edddd9688c20515421d (opens in a new tab)
- https://git.kernel.org/stable/c/37010021d7e0341bb241ca00bcbae31f2c50b23f (opens in a new tab)
- https://git.kernel.org/stable/c/7e4d9120cfa413dd34f4f434befc5dbe6c38b2e5 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-203677 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-68219)Record last updated .