ksmbd: fix potencial OOB in get_file_all_info() for compound requests
Summary
| CVE | CVE-2026-31433 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-04-22 09:16:21 UTC |
| Updated | 2026-04-22 09:16:21 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix potencial OOB in get_file_all_info() for compound requests
When a compound request consists of QUERY_DIRECTORY + QUERY_INFO
(FILE_ALL_INFORMATION) and the first command consumes nearly the entire
max_trans_size, get_file_all_info() would blindly call smbConvertToUTF16()
with PATH_MAX, causing out-of-bounds write beyond the response buffer.
In get_file_all_info(), there was a missing validation check for
the client-provided OutputBufferLength before copying the filename into
FileName field of the smb2_file_all_info structure.
If the filename length exceeds the available buffer space, it could lead to
potential buffer overflows or memory corruption during smbConvertToUTF16
conversion. This calculating the actual free buffer size using
smb2_calc_max_out_buf_len() and returning -EINVAL if the buffer is
insufficient and updating smbConvertToUTF16 to use the actual filename
length (clamped by PATH_MAX) to ensure a safe copy operation. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected f2283680a80571ca82d710bc6ecd8f8beac67d63 3a852f9d1c981fb14f6bf4e24999e0ea8088a7d7 git |
Not specified |
| CNA |
Linux |
Linux |
affected 9f297df20d93411c0b4ddad7f88ba04a7cd36e77 4cca3eff2099b18672934a39cee70aed835d652c git |
Not specified |
| CNA |
Linux |
Linux |
affected e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d 358cdaa1f7fbf2712cb4c5f6b59cb9a5c673c5fe git |
Not specified |
| CNA |
Linux |
Linux |
affected e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d 7aec5a769d2356cbf344d85bcfd36de592ac96a5 git |
Not specified |
| CNA |
Linux |
Linux |
affected e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d b0cd9725fe2bcc9f37d096b132318a9060373f5d git |
Not specified |
| CNA |
Linux |
Linux |
affected e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d 9d7032851d6f5adbe2739601ca456c0ad3b422f0 git |
Not specified |
| CNA |
Linux |
Linux |
affected e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d beef2634f81f1c086208191f7228bce1d366493d git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.6 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.203 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.168 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.131 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.80 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.21 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.19.11 6.19.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/358cdaa1f7fbf2712cb4c5f6b59cb9a5c673c5fe |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/4cca3eff2099b18672934a39cee70aed835d652c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/7aec5a769d2356cbf344d85bcfd36de592ac96a5 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/b0cd9725fe2bcc9f37d096b132318a9060373f5d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/3a852f9d1c981fb14f6bf4e24999e0ea8088a7d7 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9d7032851d6f5adbe2739601ca456c0ad3b422f0 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/beef2634f81f1c086208191f7228bce1d366493d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.