Latest from Embedded

ID 124110546 © Maciek905 | Dreamstime.com
code_dreamstime_l_124110546
ID 23655199 © Pere Sanz | Dreamstime.com
oscilloscope_dreamstime_l_23655199
Leandro DRS
image
Dreamstime_Prostockstudio_371930154
dreamstime_ai__prostockstudio_371930154
100269668 © Ronstik | Dreamstime.com
promo_100269668__ronstik__dreamstime
ID 66792575 © Anton Matveev | Dreamstime.com
helicoptercontrolpanel_dreamstime_l_66792575
Dreamstime_Iuliia-Chernyshenko_156096018
dreamstime_iuliiachernyshenko_156096018
ID 9517116 © Plmrue | Dreamstime.com
vu_meter_dreamstime_l_9517116
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.