Firmware memory corruption via unchecked I2C writes
Published Sep 14, 2026 · Updated Sep 14, 2026
Out-of-bounds write in Zephyr RTOS 4.2.0 through 4.4.1 allows physically proximate attackers to crash controllers via oversized I2C writes. In target_i2c_isr_fifo(), the driver appends host-supplied bytes to target_in_buffer before checking the cumulative w_index against the 256-byte buffer. The flaw requires I2C target buffer mode on an it51xxx device; a master on the same bus can corrupt adjacent firmware data, causing a crash or code execution.
Summary
What happened
Out-of-bounds write in Zephyr RTOS 4.2.0 through 4.4.1 allows physically proximate attackers to crash controllers via oversized I2C writes. In target_i2c_isr_fifo(), the driver appends host-supplied bytes to target_in_buffer before checking the cumulative w_index against the 256-byte buffer. The flaw requires I2C target buffer mode on an it51xxx device; a master on the same bus can corrupt adjacent firmware data, causing a crash or code execution.
The record
- CVE
- CVE-2026-14986
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- Unavailable
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.2.0 <4.4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo