{"apiVersion":"1.0","identifier":"CVE-2026-99272","description":"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.","publishedAt":"2026-11-07T14:17:02","lastModifiedAt":"2026-11-07T14:17:02","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-99272","cvssScore":null,"cvssVector":null,"epssProbability":0.00145,"riskScore":null,"affectedProduct":"Linux kernel","affectedVersions":"unknown","vulnerabilityType":"Kernel","operatingSystems":[],"links":{"self":"https://www.redsauce.net/api/cves/CVE-2026-99272","webPages":{"es":"https://www.redsauce.net/es/cves/CVE-2026-99272","en":"https://www.redsauce.net/en/cves/CVE-2026-99272","fr":"https://www.redsauce.net/fr/cves/CVE-2026-99272","pt":"https://www.redsauce.net/pt/cves/CVE-2026-99272","de":"https://www.redsauce.net/de/cves/CVE-2026-99272","sk":"https://www.redsauce.net/sk/cves/CVE-2026-99272","el":"https://www.redsauce.net/el/cves/CVE-2026-99272"},"source":"https://nvd.nist.gov/vuln/detail/CVE-2026-99272"}}