ksmbd: validate compound request size before reading StructureSize2
Summary
| CVE | CVE-2026-64578 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-05 08:16:37 UTC |
| Updated | 2026-08-05 08:16:37 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate compound request size before reading StructureSize2 When ksmbd validates a compound (chained) SMB2 request, ksmbd_smb2_check_message() reads pdu->StructureSize2 without first checking that the compound element is large enough to contain it. StructureSize2 is a 2-byte field at offset 64 (__SMB2_HEADER_STRUCTURE_SIZE) from the start of each element. The compound-walking logic only guarantees that a full 64-byte SMB2 header is present for the trailing element: when NextCommand is 0, len is reduced to the number of bytes remaining after next_smb2_rcv_hdr_off. A remote client can craft a compound request whose last element has exactly 64 bytes, so the 2-byte StructureSize2 read at offset 64 extends one byte past the receive buffer, producing a slab-out-of-bounds read. BUG: KASAN: slab-out-of-bounds in ksmbd_smb2_check_message (fs/smb/server/smb2misc.c:402) Read of size 2 at addr ffff888012ae31ac by task kworker/0:1/14 The buggy address is located 172 bytes inside of allocated 173-byte region Workqueue: ksmbd-io handle_ksmbd_work Call Trace: ... kasan_report (mm/kasan/report.c:595) ksmbd_smb2_check_message (fs/smb/server/smb2misc.c:402) handle_ksmbd_work (fs/smb/server/server.c:119) process_one_work (kernel/workqueue.c:3314) worker_thread (kernel/workqueue.c:3397) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) Reject any compound element that is too small to hold StructureSize2 before dereferencing it. |
Risk And Classification
EPSS: 0.001560000 probability, percentile 0.052620000 (date 2026-08-07)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 2c307126ed8e7adddab82b8e31d962d3a2156ab1 git | Not specified |
| CNA | Linux | Linux | affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 f7550a91ab211726f59cb137523b7a9eae1ac6eb git | Not specified |
| CNA | Linux | Linux | affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 f0e337e7db67cc1c832958bbb6c4026bdceacfdb git | Not specified |
| CNA | Linux | Linux | affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 ea128f06d2fb2186f0cac0c9f3e953e4d1f5c29a git | Not specified |
| CNA | Linux | Linux | affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 15b38176fd1530372905c602fde51fe89ec8c877 git | Not specified |
| CNA | Linux | Linux | affected 5.15 | Not specified |
| CNA | Linux | Linux | unaffected 5.15 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.148 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.101 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.42 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.6 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2-rc4 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/f0e337e7db67cc1c832958bbb6c4026bdceacfdb | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f7550a91ab211726f59cb137523b7a9eae1ac6eb | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ea128f06d2fb2186f0cac0c9f3e953e4d1f5c29a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/15b38176fd1530372905c602fde51fe89ec8c877 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/2c307126ed8e7adddab82b8e31d962d3a2156ab1 | 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.