CVE
Zephyr kernel privilege escalation via charger driver API
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.3.2, 4.5.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. CONFIG_USERSPACE enabled Attacker thread is user-mode and has been granted a charger device object Charger driver implements the notifier properties (MAX20335, PF1550 or BQ2518x) and stores the pointer
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.11% · 1st percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Read the original 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.
Who should check
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
Not fixed by: Release lines that have not yet taken the backport remain affected.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.8/10CVSS 7.8
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
CONFIG_USERSPACE enabled Attacker thread is user-mode and has been granted a charger device object Charger driver implements the notifier properties (MAX20335, PF1550 or BQ2518x) and stores the pointerUpgrade to a fixed version: 4.3.2, 4.5.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-91007 (Arbitrary supervisor-mode function pointer injection via charger_set_prop() syscall in the charger driver API), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-91007 (entry last updated 2026-11-12):
Affected:
- zephyrproject zephyr: from 3.7.0, fixed in 4.3.2; from 4.4.0, fixed in 4.5.0
Fixed versions: 4.3.2, 4.5.0.
Conditions (all must be true for the bug to be hit):
- CONFIG_USERSPACE enabled (source: https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-jr35-f52j-fm88)
- Attacker thread is user-mode and has been granted a charger device object (source: https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-jr35-f52j-fm88)
- Charger driver implements the notifier properties (MAX20335, PF1550 or BQ2518x) and stores the pointer (source: https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-jr35-f52j-fm88)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-91007 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-91007 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/zephyrproject-rtos/zephyr/commit/5467b7a73fe093d7e9562ee15c321cf8f1639d17
- https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-jr35-f52j-fm88
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-91007
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-91007"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- zephyr
From 3.7.0 · fixed in 4.3.2; From 4.4.0 · fixed in 4.5.0
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-91007
Is CVE-2026-91007 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
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.Source: github.com
Which versions are affected by CVE-2026-91007?
zephyr: from 3.7.0 before 4.3.2; from 4.4.0 before 4.5.0.Source: cve.now feed data
Am I affected, and how do I check?
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.Source: github.com
How do I fix CVE-2026-91007?
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.Source: github.com