llamaCVEVulnerability Intelligence
/
Zephyr

CVE-2026-91007

Zephyr kernel privilege escalation via charger driver API

A low-privilege user thread can run arbitrary code in kernel mode through charger callbacks.

Specific setups onlyParche disponibleuntrusted pointer dereference
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ón6 dDesde la divulgación, 12 nov 2026, 10:19 a. m.
Detección8 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 +2
Fuente: OSV
Verificada
12 nov 26
15 nov 26
17 nov 26
19 nov 26
12 nov 26
14 nov 26
16 nov 26
17 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-91007 divulgada · CVSS 7.8 (CNA)
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: NIST NVD Registro visto por primera vez en NIST NVD
Monitoreo Fuente: ENISA EUVD Registro visto por primera vez en ENISA EUVD
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Modificada Última actualización del registro
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 12 nov 2026

Zephyr's charger driver API lets a local user-mode thread with low privileges, once it has been granted a charger device object, set arbitrary function pointers as charger notifier callbacks that the driver later calls in supervisor mode. An attacker can use this to hijack control flow at kernel privilege, bypassing the user-mode isolation that CONFIG_USERSPACE provides, and can also read a kernel code address and suppress charger notifications.

Affects Zephyr 3.7.0 to before 4.3.2 and 4.4.0 to before 4.5.0 with CONFIG_USERSPACE and a user-mode thread granted a charger device on MAX20335, PF1550 or BQ2518x. Fixed in 4.3.2 and 4.5.0.

¿Qué significa?A user-mode thread that has been granted a charger device object can use the charger_set_prop() syscall to store a function pointer that the kernel later calls at supervisor privilege. This is a control-flow hijack that defeats CONFIG_USERSPACE isolation, and it can also disclose kernel code addresses and suppress charger notifications.
¿Quién está afectado?Zephyr 3.7.0 up to 4.3.2 and 4.4.0 up to 4.5.0 are in range when CONFIG_USERSPACE is enabled and the charger driver is MAX20335, PF1550 or BQ2518x, which store the notifier pointer. Check CONFIG_USERSPACE in the build configuration and which charger driver the board uses.
¿Qué hacer?Upgrade Zephyr to 4.3.2 or 4.5.0, the fixed version for each affected line. The facts name no vendor patch IDs or workaround.
Descripción original del registro (zephyr)

The user-mode syscall verifiers for the charger driver API in drivers/charger/charger_handlers.c did not inspect the prop argument before copying union charger_propval across the user/kernel boundary. Two members of that union are function pointers — status_notification (CHARGER_PROP_STATUS_NOTIFICATION) and online_notification (CHARGER_PROP_ONLINE_NOTIFICATION), declared in include/zephyr/drivers/charger.h — and z_vrfy_charger_set_prop() forwarded the caller-supplied union verbatim to the driver's set_property callback for any property. z_vrfy_charger_get_prop() had the mirror defect and copied the stored kernel callback address back out to user memory. With CONFIG_USERSPACE enabled, any user-mode thread that has been granted a charger device object could call charger_set_prop() with CHARGER_PROP_STATUS_NOTIFICATION or CHARGER_PROP_ONLINE_NOTIFICATION and an arbitrary pointer value. Drivers that implement these properties — drivers/charger/charger_max20335.c, drivers/charger/charger_pf1550.c and drivers/charger/charger_bq2518x.c — store the pointer in device data and later invoke it from their interrupt work handlers, which run in supervisor mode, on any charger state change such as a cable plug/unplug. The result is a control-flow hijack at kernel privilege from an unprivileged thread, defeating the isolation that CONFIG_USERSPACE is meant to provide; the read path additionally disclosed a kernel code address to user mode, and clearing a notifier installed by a supervisor thread let user mode suppress charger notifications. Supervisor-mode callers of charger_set_prop()/charger_get_prop() are unaffected. The fix makes both verifiers reject the two notifier properties outright — including when the supplied callback is NULL, since the notifiers are device state — and adds a BUILD_ASSERT on CHARGER_PROP_COMMON_COUNT so that new properties force a re-review of the union's user-mode safety.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
CONFIG_USERSPACE enabled“With CONFIG_USERSPACE enabled”
02
Attacker thread is user-mode and has been granted a charger device object“any user-mode thread that has been granted a charger device object”
03
Charger driver implements the notifier properties (MAX20335, PF1550 or BQ2518x) and stores the pointer“store the pointer in device data and later invoke it”
¿Quién debe revisar?Zephyr users with CONFIG_USERSPACE enabled on charger drivers (MAX20335, PF1550, BQ2518x) in versions 3.7.0 up to 4.3.2 and 4.4.0 up to 4.5.0
No protegeRelease 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.7.0 < 4.3.2
zephyr≥ 4.4.0 < 4.5.0
3.7.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-jr35-f52j-fm88
Parchehttps://github.com/zephyrproject-rtos/zephyr/commit/5467b7a73fe093d7e9562ee15c321cf8f1639d17

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