search
Zephyr
Trends
- 1Texas Instruments Adopts Zephyr RTOS Across Embedded Portfolio▼TI Integrates Open-Source RTOS Zephyr Across Entire Embedded Portfolio
Texas Instruments has integrated the open-source Zephyr real-time operating system across its entire embedded processor portfolio, letting developers use a single, vendor-supported RTOS across its microcontrollers and processors. The move aligns TI with the growing industry shift toward open-source embedded software and should simplify development for engineers working across multiple TI chip families.
- 2Texas 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.
- 3Texas Instruments and Infineon Upgrade to Zephyr Platinum Membership▼Zephyr Project Expands Semiconductor Industry Support as Texas Instruments and Infineon Technologies Upgrade to Platinum Membership
Texas Instruments and Infineon Technologies have upgraded to Platinum membership of the Zephyr Project, expanding semiconductor industry support for the open-source real-time operating system. The move strengthens the project's backing among major chipmakers and signals growing industry investment in Zephyr as a foundation for embedded and connected devices.
- 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.