CVE-2026-91007

7.8High

Published 12 Nov 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.1-flash-lite

7.8CVSS

High

0CVSS v3.110

Attack vector
Local
Complexity
Low
Privileges
Low
User action
None
Impact
Full C/I/A compromise
Weakness
CWE-822

What an attacker gets

Local attackers can hijack kernel control flow to gain full system privileges. They need an account with access to a charger device object on a system where CONFIG_USERSPACE is enabled.

Root cause

The charger driver syscall verifiers fail to validate the prop argument, allowing user-mode threads to pass arbitrary function pointers into the kernel.

Affected versions

Zephyr RTOS versions prior to the fix in commit 5467b7a73fe093d7e9562ee15c321cf8f1639d17.

CVSS v3.1 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Fix & remediation

Update to a patched Zephyr release containing the fix for GHSA-jr35-f52j-fm88. If you cannot update, disable access to charger device objects for unprivileged user threads.

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD description

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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-91007