Causes of memory unsafety
In our first blog in this series, we looked at the high costs associated with memory safety failures. In the second post we saw that commonly used methods to ensure processor integrity were not adequate. This means that memory unsafety is a characteristic of many of today’s systems. In this blog we look at some of the causes of memory unsafety.
What is memory unsafety?
In our previous blog post we looked at buffer bounds problems such as buffer overflows and over-reads. The root cause of these vulnerabilities is unsafe programming. Major software vendors consistently report memory unsafety problems. For example, the Chromium open-source browser project has stated that 69% of CVEs (Common Vulnerabilities and Exposures) reported relate to memory unsafety.
To read the full article, click here
Related Semiconductor IP
- 64 bit RISC-V Multicore Processor with 2048-bit VLEN and AMM
- RISC-V AI Acceleration Platform - Scalable, standards-aligned soft chiplet IP
- 32 bit RISC-V Multicore Processor with 256-bit VLEN and AMM
- All-In-One RISC-V NPU
- ISO26262 ASIL-B/D Compliant 32-bit RISC-V Core
Related Blogs
- The Importance of Memory Architecture for AI SoCs
- SSD Interfaces and Performance Effects
- What’s on the Horizon for NAND and DRAM?
- DDR3/DDR2 price crossover reached
Latest Blogs
- Trust at the Core: A Deep Dive into Hardware Root of Trust (HRoT)
- Himax Accelerates Chip Design with Cadence Cerebrus Intelligent Chip Explorer
- LPDDR6: The Next-Generation LPDDR Device Standard and How It Differs from LPDDR5
- MIPI MPHY 6.0: Enabling Next-Generation UFS Performance
- How Does Crocodile Dundee Relate to AI Inference?