Latest from Embedded

100269668 © Ronstik | Dreamstime.com
promo_100269668__ronstik__dreamstime
Irina Toloknovskaia, Dreamstime.com
Circuit Diagram51965608 © Irina Toloknovskaia Dreamstime
ID 122748715 - Design © Everythingpossible - Dreamstime.com
Planner manipulating chart
ID 340558606 - Ai © Yulia Gapeenko - Dreamstime.com
promo__id_340558606__ai__yulia_gapeenko__dreamstim
Dreamstime_thekaikoro_137795256
dreamstime_thekaikoro_137795256_promo
ID 317960473 | Ai Communications © Neirfy | Dreamstime.com
digital_dreamstime_l_317960473
Codasip
65e896b988f459001eded7ac Promo Codasipcheritechnology

What’s the Difference Between Conventional Memory Protection and CHERI? (Download)

March 6, 2024

Read this article online.

Most semiconductor companies and OEMs take precautions around processor-based systems, which includes secure boot and encrypting communications of important data. However, relatively little attention has been given to memory safety vulnerabilities like buffer overflows or over-reads when designing systems on chip (SoCs). 

Such weaknesses have been exploited time and time again, usually at great cost for users and suppliers of systems. For decades, industry has created billions of lines of unsafe C & C++ code. However, addressing the resulting memory safety risks has been discussed little outside software groups. 

Comments

To join the conversation, and become an exclusive member of Electronic Design, create an account today!