<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cpe:2.3:a:zephyr_project:zephyr_rtos:*:*:*:*:*:*:*:* - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3azephyr_projectzephyr_rtos/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 12 Nov 2026 17:01:31 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3azephyr_projectzephyr_rtos/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Zephyr RTOS: Charger driver API privilege escalation (CVE-2026-91007)</title><link>https://feed.craftedsignal.io/briefs/2026-11-zephyr-charger-syscall-vulnerability-cve-2026-91007/</link><pubDate>Thu, 12 Nov 2026 17:01:31 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-zephyr-charger-syscall-vulnerability-cve-2026-91007/</guid><description>A vulnerability in the Zephyr RTOS charger driver API allows unprivileged user-mode threads to trigger a kernel-mode control-flow hijack due to insufficient syscall verification of function pointers in a union.</description><content:encoded><![CDATA[<p>CVE-2026-91007 involves an improper validation of the charger_propval union within the charger driver API in drivers/charger/charger_handlers.c. User-mode syscall verifiers z_vrfy_charger_set_prop() and z_vrfy_charger_get_prop() failed to inspect the prop argument before copying data across the user/kernel boundary. This allowed user-mode threads to pass arbitrary function pointers for the CHARGER_PROP_STATUS_NOTIFICATION or CHARGER_PROP_ONLINE_NOTIFICATION properties. These pointers are stored in device data by specific drivers (MAX20335, PF1550, and BQ2518x) and subsequently invoked from supervisor-mode interrupt work handlers.</p>
<h2 id="impact">Impact</h2>
<p>This vulnerability permits kernel-mode control-flow hijacking from an unprivileged thread, bypassing isolation provided by CONFIG_USERSPACE. Additionally, it facilitates kernel code address disclosure to user memory and allows the suppression of charger notifications.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Apply the patch that updates the syscall verifiers to reject notifier properties and incorporates a BUILD_ASSERT on CHARGER_PROP_COMMON_COUNT to ensure future property additions are validated for user-mode safety.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cve</category><category>privilege-escalation</category><category>kernel-vulnerability</category><category>rtos</category></item></channel></rss>