VulnWatch by ve1ve2

CVE-2026-99272

unknown awaiting NVD score — see report severities below NVD ↗CVE.org ↗

In the Linux kernel, the following vulnerability has been resolved: smb: client: validate the data area in SMB2_read() SMB2_read() copies le32_to_cpu(rsp->DataLength) bytes from (char *)rsp + rsp->DataOffset without checking that the range lies within the response actually received. A READ response with DataOffset == 0 makes smb2_get_data_area_len() zero the data length, so smb2_check_message() accepts a frame as short as the fixed response, while SMB2_read() still uses the server-supplied DataLength, capped only by CIFS_MAX_MSGSIZE and the caller's length. A malicious server can answer the synchronous read used by the mfsymlinks (or SFU) symlink parser with an 81-byte READ response carrying DataOffset 0 and DataLength 1067, making the client copy 1067 bytes from a 448-byte receive object (KASAN slab-out-of-bounds; up to 16 KiB in the general case). Clamp a zero (or header-overlapping) DataOffset to read_rsp_size, as handle_read_data() does for the asynchronous path, and reject the response unless DataOffset + DataLength fits within rsp_iov.iov_len. The SMB1 helper was fixed the same way in 5be5bdda5863.

CVSS:
—
EPSS:
0.20% (percentile 9.6)
Published:
Modified:
First seen:
NVD status:
Received
Aliases:
CVE-2026-99275, CVE-2026-99308, CVE-2026-99312, CVE-2026-99314, CVE-2026-99315, CVE-2026-99316, CVE-2026-99317, CVE-2026-99318, CVE-2026-99319, CVE-2026-99320, CVE-2026-99335, CVE-2026-99336, CVE-2026-99345, CVE-2026-99347, CVE-2026-99348, CVE-2026-99350, CVE-2026-99363, CVE-2026-99376, CVE-2026-99377, CVE-2026-99379, CVE-2026-99382, CVE-2026-99384, CVE-2026-99387, CVE-2026-99394, CVE-2026-99426, CVE-2026-99484, CVE-2026-99496, CVE-2026-99566, CVE-2026-99567, CVE-2026-99568, CVE-2026-99569, CVE-2026-99570, CVE-2026-99573, CVE-2026-99574, CVE-2026-99575, CVE-2026-99576, CVE-2026-99577, CVE-2026-99578, CVE-2026-99579, CVE-2026-99580, CVE-2026-99582, CVE-2026-99583, CVE-2026-99587, CVE-2026-99588, CVE-2026-99589, CVE-2026-99590, CVE-2026-99591, CVE-2026-99593, CVE-2026-99594

JSON

Reports (2)