CVE-2026-14367

Device crash via unsynchronized I3C work-node free list

Published Aug 31, 2026 · Updated Sep 1, 2026

Race condition in Zephyr RTOS 3.2.0 through 4.4.1 allows physically proximate attackers to crash or hang devices via I3C bus traffic. The IBI enqueue paths remove nodes from i3c_ibi_work_nodes_free in interrupt context while the workqueue handler appends nodes without synchronization, corrupting list links and enabling stale-pointer writes. Exploitation requires control of an on-board I3C peripheral and a narrow timing collision; the expected result is a device crash or hang, while memory corruption is less controllable.

CVSS severity3.1
Low
EPSS probability0.10%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Race condition in Zephyr RTOS 3.2.0 through 4.4.1 allows physically proximate attackers to crash or hang devices via I3C bus traffic. The IBI enqueue paths remove nodes from i3c_ibi_work_nodes_free in interrupt context while the workqueue handler appends nodes without synchronization, corrupting list links and enabling stale-pointer writes. Exploitation requires control of an on-board I3C peripheral and a narrow timing collision; the expected result is a device crash or hang, while memory corruption is less controllable.

The record

CVE
CVE-2026-14367
Published
Aug 31, 2026
Updated
Sep 1, 2026
Vendor
Zephyr Project
Product
Zephyr RTOS
Classifications
CWE-362, T0814
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 31, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 1, 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.

  1. Affected versionversion=3.2.0 <4.4.2

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

Zephyr Project · Zephyr RTOSversion=3.2.0 <4.4.2

Published CVSS scores

3.1Zephyr ProjectCVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
T0814Denial of Service

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