CVE-2026-99273
Linux kernel out-of-bounds write in ksmbd stream info
An attacker who can reach the file server can write two bytes past a response buffer, corrupting nearby memory.
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-99273 divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Fuente: PoC-in-GitHub | Registro visto por primera vez en PoC-in-GitHub | |
| Monitoreo | Fuente: OSV | Registro visto por primera vez en OSV | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
The Linux kernel's ksmbd SMB file server can write two bytes past the end of a response buffer when it builds file stream information, because the space for the UTF-16 string terminator was not reserved. The fix reserves that space, and the reported lengths stay the same.
Descripción original del registro (Linux)
In the Linux kernel, the following vulnerability has been resolved: ksmbd: reserve space for the UTF-16 terminator in stream info smb_strtoUTF16() always writes a terminating zero UTF-16 unit after the converted characters, but get_file_stream_info() budgets only sizeof(struct smb2_file_stream_info) + streamlen * 2 for a stream entry and sizeof(struct smb2_file_stream_info) + 7 * 2 for the trailing "::$DATA" entry. When an entry exactly fills the 448-byte small response buffer, the terminator is written two bytes past the allocation. Reserve one extra UTF-16 unit in both budget checks. The terminator is not part of the wire format, so the reported lengths are unchanged.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Linux |
Corregida | 6.12.117, 6.18.61, 7.3.2 | — | — |
6.12.1176.18.617.3.2Arsenal público
Ver los 1 repositorios de GitHub
Los repositorios públicos incluyen exploits, escáneres, laboratorios y reglas de detección. No ejecute código de terceros sin revisarlo en un entorno aislado.
https://git.kernel.org/stable/c/583ede545a14f275a959772b5e1e50fe3e14b861https://git.kernel.org/stable/c/06a751809ebd33e95b05bf733697318a17a4872bhttps://git.kernel.org/stable/c/0e64f89563164719ceb1aa33f2a8bfd6391fa340https://git.kernel.org/stable/c/a025c4991a7d83edc4dd339e3ea86d8ff6226ecahttps://github.com/googlesky/CVE-2026-99273Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
