llamaCVEVulnerability Intelligence
/
zephyr

CVE-2026-87041

Inverted memory-permission check in the RTIO syscall verifier allows a user-mode thread to read and write arbitrary kernel memory

Specific setups onlyParche disponibleout-of-bounds read
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ó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-87041 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 RTIO submission-queue verifier rtio_vrfy_sqe() in subsys/rtio/rtio_syscalls.c (subsys/rtio/rtio_handlers.c before v4.3.0) accumulated the results of K_SYSCALL_MEMORY() into its valid_sqe flag with &=. That macro returns nonzero on failure (it is built on K_SYSCALL_VERIFY_MSG(), which yields !(expr)), so every buffer permission check contributed the opposite of its result. A submission whose tx.buf, rx.buf or txrx.tx_buf/txrx.rx_buf pointer was not accessible to the calling thread was accepted, while a legitimate, thread-owned buffer caused the calling thread to be killed with a kernel oops. The verifier runs on behalf of the rtio_sqe_copy_in_get_handles() system call (also reached through the inline rtio_sqe_copy_in() wrapper), so it is driven directly by untrusted user-mode input on any image built with CONFIG_USERSPACE. A user thread that has been granted an RTIO context and an rtio_iodev object — the intended usage of RTIO userspace support, established via rtio_access_grant() — can submit an SQE whose buffer pointer and length name arbitrary kernel memory; the object check on sqe->iodev is unaffected and still passes, and the crafted SQE is forwarded to the bus driver unchanged. Downstream consumers dereference the pointer with supervisor privilege. The generic I2C and I3C RTIO fallback handlers (drivers/i2c/i2c_rtio_default.c, drivers/i3c/i3c_rtio_default.c) copy sqe.rx.buf/sqe.tx.buf into struct i2c_msg and call i2c_transfer(), and the vendor SPI/I2C RTIO drivers behave equivalently. An RTIO_OP_RX submission therefore has peripheral data written into kernel memory of the attacker's choosing (arbitrary kernel write), an RTIO_OP_TX submission clocks kernel memory out over the bus (kernel memory disclosure), and a pointer to unmapped memory faults the kernel. This is a full escape from the user-mode isolation boundary that CONFIG_USERSPACE exists to enforce. The defect was masked for years because the in-tree user-mode RTIO tests only exercise RTIO_OP_NOP and mempool-backed reads, neither of which reaches the affected checks. The fix negates each K_SYSCALL_MEMORY() result and additionally validates the TXRX transmit buffer read-only, matching the SPI, I2C and I3C handlers.

Only Zephyr builds with CONFIG_USERSPACE and CONFIG_RTIO both enabled are affected, and only for threads granted an RTIO context and rtio_iodev. Fixed in 4.3.2 and 4.5.0.

¿Qué significa?The RTIO syscall verifier checks memory permissions backwards, which lets a user-mode thread read and write arbitrary kernel memory. This is a full escape from the user-mode isolation that CONFIG_USERSPACE is meant to enforce. An invalid pointer can also fault the kernel.
¿Quién está afectado?Zephyr 3.3.0 up to 4.3.2 and 4.4.0 up to 4.5.0 are in the affected ranges, but only in builds with both CONFIG_USERSPACE and CONFIG_RTIO enabled, and only for threads granted an RTIO context and an rtio_iodev object. To check a build, look at whether these two options are set in its Kconfig configuration and which Zephyr version it was built from.
¿Qué hacer?Upgrade to Zephyr 4.3.2 or 4.5.0, which contain the fix. The sources provided do not list a workaround.
Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Zephyr built with CONFIG_USERSPACE and CONFIG_RTIO enabled“Severity is High conditional on enabling CONFIG_USERSPACE together with CONFIG_RTIO”
02
The attacker thread must have been granted an RTIO context and an rtio_iodev object“A user thread that has been granted an RTIO context and an rtio_iodev object”
03
Affected release lines are 3.3.0 up to 4.3.2 and 4.4.0 up to 4.5.0“Release lines that have not yet taken 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≥ 3.3.0 < 4.3.2
zephyr≥ 4.4.0 < 4.5.0
3.3.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-mvxr-jx9h-jxh4
Parchehttps://github.com/zephyrproject-rtos/zephyr/commit/454a848006595ce2d77fc2c9e458b0c557f5e4af

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