llamaCVEVulnerability Intelligence
/
zephyr

CVE-2026-87039

I2S configure syscall handler passes an unvalidated user-supplied kernel object pointer to drivers

Specific setups onlyParche disponibleout-of-bounds write
Descargar PNG JSON
CVSS 3.1
7.8
Alta
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H Fuente: CNA
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versión4.5.0
Exposición15 dDesde la divulgación, 4 nov 2026, 1:09 a. m.
Detección5 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir de cerca
Monitorear y programar la remediación
Sin explotación conocida, no automatizable e impacto técnico total. Hay versiones corregidas disponibles.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC +1
Explotación
Remediación
Monitoreo
Detectada +1
Fuente: OSV
Verificada
4 nov 26
9 nov 26
16 nov 26
19 nov 26
4 nov 26
8 nov 26
11 nov 26
15 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-87039 divulgada · CVSS 7.8 (CNA)
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: NIST NVD Registro visto por primera vez en NIST NVD
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Modificada Última actualización del registro
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Monitoreo Verificada Última verificación contra las fuentes
Resumen

The user-mode syscall verifier z_vrfy_i2s_configure() in drivers/i2s/i2s_handlers.c copies the caller's struct i2s_config in from user memory and then, when cfg->frame_clk_freq is 0 (the API's "unconfigure the stream" request), jumps straight to z_impl_i2s_configure() without performing the K_SYSCALL_OBJ(config.mem_slab, K_OBJ_MEM_SLAB) ownership/type check or the block_size sanity check. The mem_slab field is a struct k_mem_slab *, so on that path a completely unvalidated, user-chosen pointer reaches driver code that is entitled to trust it as a real kernel object. Any thread running under CONFIG_USERSPACE that has access to an I2S device object can trigger this with a single i2s_configure() call. Most in-tree drivers special-case frame_clk_freq == 0 and never store the caller's structure, but drivers/i2s/i2s_litex.c does not: i2s_litex_configure() only logs a warning for a mismatched frame clock, then memcpy()s the caller's config into stream->cfg and marks the stream I2S_STATE_READY. A subsequent i2s_trigger() with I2S_TRIGGER_START enables the FIFO interrupt, and the interrupt handlers i2s_litex_isr_rx() / i2s_litex_isr_tx() then call k_mem_slab_alloc() and k_mem_slab_free() on the attacker-supplied pointer in supervisor context. The result is an arbitrary-pointer read/write primitive executed by the kernel on behalf of an unprivileged thread — k_mem_slab_alloc() takes a spinlock at slab->lock and reads and writes slab->free_list and the link word inside the returned "block" — which defeats the CONFIG_USERSPACE isolation boundary entirely. The same missing validation is a hazard for out-of-tree I2S drivers that retain the configuration on the unconfigure path. Builds without CONFIG_USERSPACE are unaffected, since the verifier is not used. The fix zeroes config.mem_slab and config.block_size on the unconfigure path so the driver can never receive an unvalidated pointer, while still allowing a stream to be unconfigured by a caller that does not own a memory slab, as the API documents.

Zephyr versions 4.4.0 up to 4.5.0 with CONFIG_USERSPACE, where a thread can reach an I2S device object, are exposed. The fix is in Zephyr 4.5.0. No vendor rating is given.

¿Qué significa?The I2S configure syscall handler passes a pointer from user space to drivers without validating it. This lets the kernel read and write memory at addresses the calling thread chooses, which breaks the isolation that CONFIG_USERSPACE provides.
¿Quién está afectado?Zephyr versions from 4.4.0 before 4.5.0. The bug needs CONFIG_USERSPACE and a thread with access to an I2S device object, and it applies to drivers that do not keep the caller's configuration on the unconfigure path, as the advisory describes for drivers/i2s/i2s_litex.c. To check, look at the Zephyr version in your tree and whether CONFIG_USERSPACE is set in your build configuration.
¿Qué hacer?Upgrade to Zephyr 4.5.0 or later, which contains the fix. The sources give no workaround.
Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Zephyr versions >= 4.4.0 and < 4.5.0“>= 4.4.0, < 4.5.0”
02
Requires CONFIG_USERSPACE and a thread with access to an I2S device object“Any thread running under CONFIG_USERSPACE that has access to an I2S device object can trigger this with a single i2s_configure() call”
03
Driver must retain the caller's configuration on the unconfigure path, as drivers/i2s/i2s_litex.c does“drivers/i2s/i2s_litex.c does not”
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:L
RedAdyacenteLocalFísica
ComplejidadAC:H
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:C
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
zephyr≥ 4.4.0 < 4.5.0
4.4.0
4.5.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
zephyr
Corregida 4.5.0 — —
Versiones corregidas4.5.0
Explotación

Arsenal público

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

Referencias
Fabricantehttps://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-g43m-x6vj-5cg2
Parchehttps://github.com/zephyrproject-rtos/zephyr/commit/e9898c4d22f69575d9b5f297b3df130ceaff1b8f

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