VulnerabilityPublished 12 Nov 2026

CVE-2026-19809: zephyrproject zephyr · Info-leak

Affects zephyrproject zephyrSource CVE Database V5

Compare

Not known to be exploited · CVSS 3.3 Low : upgrade to 4.5.0 or 4.3.2 when convenient.

Data as of 12 Nov 2026, 15:48 UTC

CVSS 3.1 base score

3.3Low

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (zephyr)	CVSS 3.1	3.3

Patch: Available – fixed in 4.5.0, 4.3.2

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade zephyrproject zephyr to 4.5.0 or 4.3.2.

Affected software

Product	Affected	Fixed in
zephyrprojectzephyr	Affected >=4.4.0 <4.5.0	Fixed in 4.5.0
zephyrprojectzephyr	Affected >=3.5.0 <4.3.2	Fixed in 4.3.2
GitHubzephyr`pkg:github/zephyr`Other threats	Affected >=3.5.0 <4.3.2 >=4.4.0 <4.5.0	Fixed in 4.3.2 4.5.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The issue is fixed in Zephyr versions 4.3.2 and 4.5.0. Users should upgrade to these or later versions to remediate the vulnerability. Both fixes—skipping copy-out on error and zeroing the union before use—are necessary to fully eliminate the leak.

Description

CVE-2026-19809 is an information leak vulnerability in the Zephyr project affecting the user-mode system call verifier function z_vrfy_charger_get_prop(). It improperly copies uninitialized kernel stack memory to user space, disclosing up to 12 or 16 bytes of kernel stack residue. This leak can reveal kernel object addresses and saved return addresses, aiding attackers in bypassing address layout randomization. The flaw affects Zephyr versions >=3.5.0 <4.3.2 and >=4.4.0 <4.5.0 and is fixed in versions 4.3.2 and 4.5.0. The vulnerability has low severity and no integrity or availability impact.

Impact

The vulnerability leaks kernel stack memory to unprivileged user-mode threads, disclosing kernel object addresses and saved return addresses. This information disclosure can assist attackers in defeating kernel address space layout randomization (KASLR) and facilitate exploitation of other memory safety bugs. There is no impact on integrity or availability.

Summary

The vulnerability arises because the function z_vrfy_charger_get_prop() declares an uninitialized union charger_propval on the kernel stack and copies its entire content back to user space regardless of whether the driver backend wrote valid data or returned an error. On error, the union remains uninitialized, leaking kernel stack contents. On success, only a part of the union is initialized, but the entire union is copied out, leaking residual stack bytes. This function is accessible to any user-mode thread with charger device access, allowing repeated leakage of kernel stack memory. Two commits fix the issue: one skips copying on error, and the other zeroes the union before use. Both fixes are required to fully resolve the leak. The flaw is present only when CONFIG_USERSPACE=y.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Nov 2026, 15:48 UTC

Technical details

References

Community reviews

Related threats