llamaCVEVulnerability Intelligence
/
zephyr

CVE-2026-87038

Time-of-check/time-of-use double fetch in the Zephyr i3c_transfer() syscall handler allows kernel-mode control-flow hijack from user mode

Specific setups onlyParche disponiblerace condition
Descargar PNG JSON
CVSS 3.1
7.0
Alta
CVSS:3.1/AV:L/AC:H/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ón6 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-87038 divulgada · CVSS 7 (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 verification handler for the i3c_transfer() system call, z_vrfy_i3c_transfer() in drivers/i3c/i3c_handlers.c, validated the caller-supplied struct i3c_device_desc in place instead of snapshotting it. It confirmed only that the descriptor was readable by the calling thread (K_SYSCALL_MEMORY_READ()), read target->bus once to check it with K_SYSCALL_OBJ(), and then passed the caller's live pointer down. The implementation z_impl_i3c_transfer() re-reads target->bus from that user memory and dispatches through it as DEVICE_API_GET(i3c, target->bus)->i3c_xfers(...), so the bus that was validated is not necessarily the bus that is used. DEVICE_API_GET() performs no runtime type check outside CONFIG_DEVICE_API_ASSERT builds. On a build with CONFIG_USERSPACE and an I3C controller driver, a user thread that has been granted an I3C device object can exploit this with a second thread in the same memory domain: one thread calls i3c_transfer() while the other rewrites the bus field of the descriptor. The window between the check and the use spans the num_msgs validation, the message-array access check, a stack VLA allocation and a memcpy() of up to 32 struct i3c_msg, so the race is repeatable and can simply be retried until it lands. When the substitution succeeds, the kernel dereferences an attacker-chosen pointer as a struct device, loads a function pointer from the attacker-controlled api table and calls it in supervisor mode with attacker-influenced arguments. This yields kernel-mode code execution from an unprivileged user thread — a complete escape of the userspace memory-protection sandbox; lesser outcomes are an arbitrary two-level kernel read or a kernel fault. Builds without CONFIG_USERSPACE, or without an I3C driver, are unaffected. The fix copies the descriptor into a kernel-stack local with k_usermode_from_copy(), validates the bus in that copy, and dispatches on the copy, so the validated value is provably the value used.

Affects Zephyr builds with CONFIG_USERSPACE and an I3C controller driver, from 3.2.0 before 4.3.2 and from 4.4.0 before 4.5.0. Fixed in 4.3.2 and 4.5.0.

¿Qué significa?The i3c_transfer() syscall handler reads a value supplied from user mode twice, once to check it and once to use it. A user thread can change the value between those two reads, so the check no longer holds. The advisory says this can lead to kernel-mode code execution from an unprivileged user thread, escaping the userspace memory-protection sandbox. Lesser outcomes it lists are an arbitrary two-level kernel read or a kernel fault.
¿Quién está afectado?Zephyr versions from 3.2.0 before 4.3.2, and from 4.4.0 before 4.5.0. The bug needs a build with CONFIG_USERSPACE enabled and an I3C controller driver. To check a build, look at the Zephyr version it was built from and at whether CONFIG_USERSPACE and an I3C controller driver are set in its configuration.
¿Qué hacer?Upgrade to Zephyr 4.3.2 if you are on the 4.3 line, or to 4.5.0 if you are on the 4.4 line. The facts give no workaround, so the fixed releases are the only stated remedy.
Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Build has CONFIG_USERSPACE and an I3C controller driver“On a build with CONFIG_USERSPACE and an I3C controller driver”
02
Affected versions are >= 3.2.0 and < 4.3.2, and >= 4.4.0 and < 4.5.0“>= 3.2.0, < 4.3.2”
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:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
zephyr≥ 3.2.0 < 4.3.2
zephyr≥ 4.4.0 < 4.5.0
3.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-86xj-2q6x-h82w
Parchehttps://github.com/zephyrproject-rtos/zephyr/commit/550437bc9efd7b733f13b9be73e77fd98858c8a2

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