CVE-2026-19737: zephyrproject zephyr · Memory-safety
Affects zephyrproject zephyrSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium : upgrade to 4.5.0 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.5.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Oct 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 17 Nov 2026.
What to do
Upgrade zephyrproject zephyr to 4.5.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| zephyrprojectzephyr | Affected
| Fixed in
|
GitHubzephyrpkg:github/zephyrOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix has been merged that adds pointer validation for unsupported I2S directions and returns an error instead of dereferencing NULL pointers. Users should upgrade to Zephyr version 4.5.0 or later where this fix is included. For affected versions (>=4.4.0 <4.5.0), apply the official patch or update to a fixed release. No additional mitigation is required as the vulnerability is addressed by the official fix.
Description
CVE-2026-19737 is a memory-safety vulnerability in the Zephyr project's i2s_esp32 driver affecting versions from 4.4.0 up to but not including 4.5.0. The issue arises when the driver dereferences NULL pointers for I2S directions not implemented by the device, leading to a kernel-mode read from address zero. This can be triggered by an unprivileged user-mode thread with access to the I2S device, causing a system-wide denial of service due to a fatal exception. The vulnerability does not allow information disclosure or code execution. A fix has been merged that adds proper pointer checks and returns an error for unsupported directions.