search
Zephyr RTOS
Trends
- 1TI extends Zephyr RTOS support across embedded portfolio▼TI extends Zephyr RTOS support across embedded product portfolio
Texas Instruments has expanded its support for the Zephyr real-time operating system across its embedded product portfolio. The move gives developers working with TI's embedded chips a broader, open-source software option, and electronics industry outlets are reporting the announcement as a notable step in the growing adoption of Zephyr in commercial embedded design.
- 2Texas Instruments Adopts Zephyr RTOS Across Embedded Portfolio▼TI Integrates Open-Source RTOS Zephyr Across Entire Embedded Portfolio
Texas Instruments has announced the integration of the open-source Zephyr real-time operating system across its entire embedded processor and microcontroller portfolio. The move gives developers a unified, vendor-supported software platform across TI chips, reducing reliance on proprietary RTOSes. Engineers are discussing what the shift means for long-term support, portability, and the broader industry trend toward open-source embedded software.
- 3Texas Instruments and Infineon Upgrade to Zephyr Platinum Membership▼Zephyr Project Expands Semiconductor Support as Texas Instruments and Infineon Upgrade to Platinum Membership
The Zephyr Project, an open-source real-time operating system hosted by the Linux Foundation, announced that Texas Instruments and Infineon have both upgraded to Platinum membership. The move expands semiconductor vendor support for Zephyr and signals growing industry investment in the open-source embedded ecosystem, with the two chipmakers expected to deepen their contributions to the project's hardware support.
- 4Zephyr RTOS vulnerability risks nonce reuse in encrypted storage●CVE-2026-15890 Zephyr: unsynchronized static nonce counter in the ITS AEAD transform. Concurrent writes can reuse an AES
A new vulnerability, CVE-2026-15890, has been disclosed in the Zephyr operating system's ITS AEAD transform. The static nonce counter is not synchronized, so concurrent writes can reuse an AES-GCM or ChaCha20-Poly1305 nonce, potentially compromising data integrity. The flaw carries a CVSS score of 5.3, and a patch is reportedly under review.