PatchSiren cyber security CVE debrief
CVE-2026-10678 zephyrproject CVE debrief
The MCTP-over-I2C+GPIO target binding in Zephyr contains a vulnerability that allows for memory corruption or denial of service. The issue arises from the processing of pseudo-register writes from an I2C bus master byte-by-byte without validating the order or the receive buffer. This vulnerability was introduced when the I2C+GPIO target binding was added and shipped in Zephyr v4.3.0 and v4.4.0, and it can be triggered by a malicious or malfunctioning controller on the bus without any prior protocol state.
- Vendor
- zephyrproject
- Product
- zephyr
- CVSS
- HIGH 8.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-21
- Original CVE updated
- 2026-07-22
- Advisory published
- 2026-07-21
- Advisory updated
- 2026-07-22
Who should care
Users of Zephyr versions 4.3.0 and 4.4.0 who utilize the MCTP-over-I2C+GPIO target binding should be aware of this vulnerability and take necessary actions to mitigate the risk. This includes reviewing system configurations, monitoring for suspicious I2C activity, and implementing compensating controls to detect and prevent exploitation.
Technical summary
The vulnerability is caused by the lack of validation for the order and receive buffer in the mctp_i2c_gpio_target_write_received() function. This allows an attacker to write an arbitrary byte through a NULL/unallocated mctp_pktbuf pointer, leading to memory corruption or a hard fault. Additionally, a one-byte heap overflow can occur when more than 255 data bytes are sent. The fix defers allocation to the first data byte with a NULL check, treats a missing length as a zero-sized packet rejected by libmctp, and moves the bounds check before the store.
Defensive priority
High
Recommended defensive actions
- Update to a fixed version of Zephyr
- Implement compensating controls to detect and prevent exploitation
- Monitor for suspicious activity on the I2C bus
- Review and update affected systems' configurations
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
Evidence notes
The vulnerability was introduced when the I2C+GPIO target binding was added and shipped in Zephyr v4.3.0 and v4.4.0. Evidence is limited to public statements from the vendor and CVE details. Defenders should verify system configurations, review logs for suspicious I2C activity, and monitor for potential memory corruption or denial of service. Additional verification tasks include checking relevant monitoring, detection, and logs for exposed assets that need extra review.
Official resources
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-07-21T22:17:00.047Z and has not been modified since then.