ksmbd: fix OOB write in QUERY_INFO for compound requests
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d · < fda9522ed6afaec45cabc198d8492270c394c7bc| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix OOB write in QUERY_INFO for compound requests
When a compound request such as READ + QUERY_INFO(Security) is received, and the first command (READ) consumes most of the response buffer, ksmbd could write beyond the allocated buffer while building a security descriptor.
The root cause was that smb2_get_info_sec() checked buffer space using ppntsd_size from xattr, while build_sec_desc() often synthesized a significantly larger descriptor from POSIX ACLs.
This patch introduces smb_acl_sec_desc_scratch_len() to accurately compute the final descriptor size beforehand, performs proper buffer checking with smb2_calc_max_out_buf_len(), and uses exact-sized allocation + iov pinning.
From the CVE record · Linux
The Linux kernel's ksmbd can write beyond an allocated response buffer while building a security descriptor. This can occur when it receives a compound request such as READ followed by QUERY_INFO(Security), and the first command consumes most of the response buffer. The input does not specify authentication requirements or the impact beyond the out-of-bounds write.
Engineers running Linux kernels with ksmbd should check their deployments; affected versions are not specified.