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
- LPDDR6: The Next-Generation LPDDR Device Standard and How It Differs from LPDDR5
- High Bandwidth Memory Evolution from First Generation HBM to the Latest HBM4
Latest Blogs
- M31 High-Speed and Long-Channel MIPI C/D-PHY Solution on TSMC N3P/N3C
- Understanding security certification and how analog IP can help
- Embedded Security explained: Secure boot for embedded systems
- World's First Standards-Compliant 112G PHY IP for Linear Optics: A Turning Point for AI Interconnects
- One Key for Every Door: How Aliro Extends the UWB Digital Key Beyond the Car