CVE-2026-52944ksmbd: fix FSCTL permission bypass by adding a permission check for FSCTL_SET_SPARSE
- 5.5MediumCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% 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: ksmbd: fix FSCTL permission bypass by adding a permission check for FSCTL_SET_SPARSE FSCTL_SET_SPARSE in fsctl_set_sparse() modifies the file's sparse attribute and saves it through xattr without any permission checks. This exposes two issues: 1) A client on a read-only share can change the sparse attribute on files it opened, even though the share is read-only. Other FSCTL write operations already check test_tree_conn_flag(work->tcon, KSMBD_TREE_CONN_FLAG_WRITABLE), but FSCTL_SET_SPARSE does not. 2) Even on writable shares, clients without FILE_WRITE_DATA or FILE_WRITE_ATTRIBUTES access should not modify the sparse attribute. Similar handle-level checks exist in other functions but are missing here. Add both share-level writable check and per-handle access check. Use goto out on error to avoid leaking file references.
Timeline
ID reserved
By Linux
- 15 days later
· 15 days later
Published
- 3 months later
· 3 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < ef664475c1bf1a27d45dae6848ca9c9c4d86853f
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 3a9a0a1c38ef90788f5d7c4b29903c8b220f744a
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 3127a884525dc8ca4def73254bfcd3ccef0bf812
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < c5ab11263e3c89aa7989afc5374ef7743e092fd0
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < de9eb0b44fa9123170e6245b49638e0e453c10f8
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < aef151bcfa494bfe983669de2726734b534adb73
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < cc57232cae23c0df91b4a59d0f519141ce9b5b02
- affected 5.15
- unaffected < 5.15
- unaffected 5.15.221 – ≤ 5.15.*
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.143 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.35 – ≤ 6.18.*
- unaffected 7.0.12 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References7
- https://git.kernel.org/stable/c/ef664475c1bf1a27d45dae6848ca9c9c4d86853f (opens in a new tab)
- https://git.kernel.org/stable/c/3a9a0a1c38ef90788f5d7c4b29903c8b220f744a (opens in a new tab)
- https://git.kernel.org/stable/c/3127a884525dc8ca4def73254bfcd3ccef0bf812 (opens in a new tab)
- https://git.kernel.org/stable/c/c5ab11263e3c89aa7989afc5374ef7743e092fd0 (opens in a new tab)
- https://git.kernel.org/stable/c/de9eb0b44fa9123170e6245b49638e0e453c10f8 (opens in a new tab)
- https://git.kernel.org/stable/c/aef151bcfa494bfe983669de2726734b534adb73 (opens in a new tab)
- https://git.kernel.org/stable/c/cc57232cae23c0df91b4a59d0f519141ce9b5b02 (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-2026-38734 (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-2026-52944)Record last updated .