CVE-2026-52944
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 6.6.143
- Linux Kernel < 6.18.35
- Linux Kernel < 7.0.12
- Linux Kernel 7.1
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-52944.md and follow it. Check whether this project is affected by CVE-2026-52944. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/3127a884525dc8ca4def73254bfcd3ccef0bf812
- https://git.kernel.org/stable/c/aef151bcfa494bfe983669de2726734b534adb73
- https://git.kernel.org/stable/c/cc57232cae23c0df91b4a59d0f519141ce9b5b02
- https://git.kernel.org/stable/c/de9eb0b44fa9123170e6245b49638e0e453c10f8
References
- https://git.kernel.org/stable/c/3127a884525dc8ca4def73254bfcd3ccef0bf812
- https://git.kernel.org/stable/c/3a9a0a1c38ef90788f5d7c4b29903c8b220f744a
- https://git.kernel.org/stable/c/aef151bcfa494bfe983669de2726734b534adb73
- https://git.kernel.org/stable/c/c5ab11263e3c89aa7989afc5374ef7743e092fd0
- https://git.kernel.org/stable/c/cc57232cae23c0df91b4a59d0f519141ce9b5b02
- https://git.kernel.org/stable/c/de9eb0b44fa9123170e6245b49638e0e453c10f8
- https://git.kernel.org/stable/c/ef664475c1bf1a27d45dae6848ca9c9c4d86853f