ksmbd: fix FSCTL permission bypass by adding a permission check for FSCTL_SET_SPARSE
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.15
References 7
git.kernel.org
- stable/c/ef664475c1bf1a27d45dae6848ca9c9c4d86853f
- stable/c/3a9a0a1c38ef90788f5d7c4b29903c8b220f744a
- stable/c/3127a884525dc8ca4def73254bfcd3ccef0bf812
- stable/c/c5ab11263e3c89aa7989afc5374ef7743e092fd0
- stable/c/de9eb0b44fa9123170e6245b49638e0e453c10f8
- stable/c/aef151bcfa494bfe983669de2726734b534adb73
- stable/c/cc57232cae23c0df91b4a59d0f519141ce9b5b02