llamaCVEVulnerability Intelligence
/
Zephyr

CVE-2026-90833

Zephyr out-of-bounds write in simulated EEPROM driver

A user-mode thread can read and overwrite kernel memory by passing a negative offset to the EEPROM API.

Specific setups onlyParche disponibleout-of-bounds write
Descargar PNG JSON
CVSS 3.1
7.8
Alta
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Fuente: CNA
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche2 versiones4.3.2 · 4.5.0
Exposición8 dDesde la divulgación, 10 nov 2026, 5:07 p. m.
Detección16 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
Fuente: OSV
Verificada
10 nov 26
13 nov 26
16 nov 26
19 nov 26
10 nov 26
13 nov 26
15 nov 26
17 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-90833 divulgada · CVSS 7.8 (CNA)
Monitoreo Detectada Ingresó al índice
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 simulated EEPROM driver validated access ranges in eeprom_range_is_valid() (drivers/eeprom/eeprom_simulator.c) with a single test, (offset + len) <= config->size. Because offset is a signed off_t and len an unsigned size_t of the same rank, the addition is evaluated in unsigned arithmetic: a negative offset combined with a compensating len wraps the sum back into the accepted range. eeprom_sim_read() and eeprom_sim_write() then memcpy() through the EEPROM(addr) macro, which is plain pointer arithmetic on the driver's static mock_eeprom array, so the copy addresses memory located before that array. eeprom_read() and eeprom_write() are __syscall entry points, and their verification handlers in drivers/eeprom/eeprom_handlers.c check only the device object and the caller's own data buffer (K_SYSCALL_MEMORY_READ/K_SYSCALL_MEMORY_WRITE) — the offset argument is passed to the driver unvalidated. With CONFIG_USERSPACE=y, a CONFIG_EEPROM_SIMULATOR device instance, and the device object granted to a user thread (the usage the in-tree tests/drivers/eeprom/api suite exercises from ZTEST_USER threads), an unprivileged thread could supply a negative offset and have the kernel perform the copy on its behalf. The result is an out-of-bounds read of kernel .bss returned into the caller's buffer and, via the write path, an out-of-bounds write of caller-supplied bytes over kernel memory preceding mock_eeprom. Both the start address and the length of the affected span are attacker-selected, so the primitive is sufficient to corrupt adjacent kernel state and escape the user-mode sandbox. Exposure is limited to builds that instantiate the simulated EEPROM (status = "okay" by default on qemu_x86 and native_sim, otherwise added by a devicetree overlay) together with userspace isolation. The fix rejects negative offsets and performs the remaining bound check without overflow.

Only affects Zephyr builds with CONFIG_USERSPACE enabled and a CONFIG_EEPROM_SIMULATOR device instance whose device object is granted to a user thread. Fixed in 4.3.2 and 4.5.0.

¿Qué significa?A signed offset bypasses the bounds check in the simulated EEPROM driver. This allows user-mode code to read kernel .bss memory into its own buffer and to write caller-supplied bytes over kernel memory, which can corrupt kernel state and escape the user-mode sandbox.
¿Quién está afectado?Zephyr 2.2.0 up to but not including 4.3.2, and 4.4.0 up to but not including 4.5.0. The setup requires CONFIG_USERSPACE=y, a CONFIG_EEPROM_SIMULATOR device instance, and that device object granted to a user thread. To check a build, look at the CONFIG_USERSPACE and CONFIG_EEPROM_SIMULATOR values in its configuration and the version in its source tree.
¿Qué hacer?Upgrade to Zephyr 4.3.2 on the 4.3 line or to 4.5.0 on the 4.5 line. The advisory names no workaround.
Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
CONFIG_USERSPACE is enabled.“With CONFIG_USERSPACE=y”
02
A CONFIG_EEPROM_SIMULATOR device instance is present.“a CONFIG_EEPROM_SIMULATOR device instance”
03
The device object is granted to a user thread.“the device object granted to a user thread”
04
Exposure is limited to builds that instantiate the simulated EEPROM.“Exposure is limited to builds that instantiate the simulated EEPROM”
¿Quién debe revisar?Teams running Zephyr 2.2.0 through 4.3.x or 4.4.x with userspace enabled and a simulated EEPROM (qemu_x86, native_sim, or devicetree-added sim EEPROM).
No protegeRelease lines without the backport remain affected.
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:L
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Versiones

Rangos afectados

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

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
zephyr
Corregida 4.3.2, 4.5.0 — —
Versiones corregidas4.3.24.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-vf6j-hcx8-44vh
Parchehttps://github.com/zephyrproject-rtos/zephyr/commit/ce2ec9b3a34d71f52f5d1d7491b91393e334713e

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