6 Lessons from the CPU Meltdown
The chief technologist of a computer hardware and software company shares some basic principles for plugging the security gaps in the next Meltdown or Spectre.
In January, Intel surprised us all with the news that it's Meltdown and Spectre CPU firmware patches were no good. The instructions were to immediately cease distributing and uploading the firmware patches.
Unfortunately, people who had downloaded the patch could not uninstall it, creating endless reboots and unpredictable system behavior. Now even AMD has joined the debacle as it faces class action lawsuits over how it responded to the flaws.
Some OEMs were better prepared than others with dedicated labs and processes to test patches before they are implemented. Others, not so much. But there are a few things we can do to help protect our customers and ourselves.
To read the full article, click here
Related Semiconductor IP
- Compact High-Speed 32-bit CPU Core
- Compact High-Speed 32-bit CPU for Real-time and Linux Applications
- Compact High-Speed 64-bit CPU for Real-time and Linux Applications
- RISC-V Processor - RV12 - 32/64 bit, Single Core CPU
- 32-bit CPU IP core - ISO 26262 Automotive Functional Safety Compliant
Related Blogs
- From ARM7 to such a Large CPU cores Port-Folio
- Migrating the CPU IP Development from MIPS to RISC-V Instruction Set Architecture
- Announcing Arm AGI CPU: The silicon foundation for the agentic AI cloud era
- The Future of Storage: From eMMC to the Blazing Speeds of UFS 5.0
Latest Blogs
- From Bug Hunting to Engineering Methodology: Lessons from AI-Driven Development
- Manufacturing Intelligence: Turning EDA Data into Trusted Action
- Execute-in-Place: Getting More from Embedded NVM
- Rethinking RTL flows with AI-driven hybrid formal verification
- Arm and NVIDIA: Building the trusted compute foundation for the agentic AI era