llamaCVEVulnerability Intelligence
/
Linux kernel

CVE-2026-99272

Linux kernel out-of-bounds read in SMB2 client READ handling

An attacker running a malicious SMB server can trigger an out-of-bounds memory read on the client.

Sin parche publicadosmb
Descargar PNG JSON
CVSS
—
N/D
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
ParcheSin parcheEl fabricante no ha publicado corrección
Exposición11 dDesde la divulgación, 7 nov 2026, 9:08 a. m.
Detección8 minDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Monitoreo
Detectada +1
Verificada
7 nov 26
17 nov 26
19 nov 26
7 nov 26
10 nov 26
13 nov 26
16 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-99272 divulgada
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: NIST NVD Registro visto por primera vez en NIST NVD
Divulgación Modificada Última actualización del registro
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 7 nov 2026

The Linux kernel's SMB client (CIFS) contains a flaw in how it handles READ responses from a server, where it can copy more data than the received response actually holds. An attacker who controls a malicious SMB server could trigger an out-of-bounds memory read on the client, though the report does not state how the attacker gains access to the client.

Descripción original del registro (Linux)

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.

Versiones

Versiones afectadas

3.7
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Linux
Sin parche — — —
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Otrahttps://git.kernel.org/stable/c/b949f6a0c08a57439334f39754ee7bd3c315d4a3
Otrahttps://git.kernel.org/stable/c/082ae8a34170b7388106aa0897f47405f0824946
Otrahttps://git.kernel.org/stable/c/1ba1937de005e261a8858f45bfef5da7458df94c
Otrahttps://git.kernel.org/stable/c/2ec9cdf469dd32bcf33073aeb30c08e9356e0ca1

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.