CVE-2026-52944

MediumCVSS 5.5/10Last modified Sep 14, 2026

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.

Metrics

CVSS 3.1 5.5/10CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected software

VendorProductVersions
LinuxLinux>= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < ef664475c1bf1a27d45dae6848ca9c9c4d86853f; >= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < 3a9a0a1c38ef90788f5d7c4b29903c8b220f744a; >= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < 3127a884525dc8ca4def73254bfcd3ccef0bf812; >= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < c5ab11263e3c89aa7989afc5374ef7743e092fd0; >= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < de9eb0b44fa9123170e6245b49638e0e453c10f8; >= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < aef151bcfa494bfe983669de2726734b534adb73; >= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < cc57232cae23c0df91b4a59d0f519141ce9b5b02
LinuxLinux5.15

References

Timeline

Published
Jun 24, 2026
Last modified
Sep 14, 2026
NVD status
Modified

Related CVEs from 2026

CVE-2026-529457.5In the Linux kernel, the following vulnerability has been resolved: Revert "wireguard: device: enable threaded NAPI" This reverts commit 9CVE-2026-529467.5In the Linux kernel, the following vulnerability has been resolved: fs/fcntl: fix SOFTIRQ-unsafe lock order in fasync signaling A SOFTIRQ-CVE-2026-529477.8In the Linux kernel, the following vulnerability has been resolved: net: qrtr: fix refcount saturation and potential UAF in qrtr_port_removCVE-2026-529485.5In the Linux kernel, the following vulnerability has been resolved: i2c: dev: prevent integer overflow in I2C_TIMEOUT ioctl While fuzzing CVE-2026-529495.5In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Fix ttm_bo_shrink() infinite LRU walk on backup failure ApplyCVE-2026-52958.0A stack buffer overflow exists in wolfSSL's PKCS7 implementation in the wc_PKCS7_DecryptOri() function in wolfcrypt/src/pkcs7.c. When procesCVE-2026-529507.8In the Linux kernel, the following vulnerability has been resolved: drm/xe/dma-buf: fix UAF with retry loop Retry doesn't work here, sinceCVE-2026-529517.8In the Linux kernel, the following vulnerability has been resolved: drm/xe/dma-buf: handle empty bo and UAF races There look to be some naCVE-2026-529528.8In the Linux kernel, the following vulnerability has been resolved: iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset ICVE-2026-529537.1In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix oops due to out of scope access Below oops triggers whCVE-2026-529547.5In the Linux kernel, the following vulnerability has been resolved: libceph: handle rbtree insertion error in decode_choose_args() A messaCVE-2026-529559.8In the Linux kernel, the following vulnerability has been resolved: libceph: Fix potential out-of-bounds access in crush_decode() A messag
CVE-2026-52944: Medium severity, CVSS 5.5 | Vulnix