News for hackers. Stuff that matters.

kwitaszczyk

Re:RISC-V Is Inevitable: State of the Union Keynote Argues on Thursday July 16, 2026 @07:51AM (#48933240)
That is not true. During the Digital Security by Design programme UKRI was shipping Morello boards to organisations that requested them. Since DSbD is over, the CHERI Alliance has taken over that initiative. You can request an Arm Morello board via the following link:

https://cheri-alliance.org/discover-cheri/cheri-products/mor...

Also, you can buy a Sonata board with CHERIoT from Mouser:

https://www.mouser.co.uk/en/ProductDetail/NewAE/NAE-SONATA-O...

Re:RISC-V Is Inevitable: State of the Union Keynote Argues on Thursday July 16, 2026 @07:48AM (#48933220)
That is not true. Two days ago lowRISC announced that OpenTitan used in Google Chromebooks will include CHERI:

https://lowrisc.org/news/opentitan-earl-grey-2-to-support-ch...

Last year, Google announced that their Coral NPU will include CHERI:

https://developers.googleblog.com/en/introducing-coral-npu-a...

There are more cores that companies are actively working on:

X730 from Codasip https://codasip.com/solutions/riscv-processor-safety-securit...

ICENI from SCI Semiconductor: https://www.scisemi.com/products/iceni-device-family/

This is a nice and easy to understand example of a memory-safety bug that CHERI [1] prevents (among other classes of vulnerabilities). Given that the SYSCTL_PROC() macro installs a pointer to an uint16_t value in the oid_arg1 field, a CHERI pure-capability kernel would construct a capability with bounds set to sizeof(uint16_t) and later the dereference of (int *)oidp->oid_arg1 in sysctl_udp_log_port() would trigger a capability bounds violation.

`sysctl -a` would simply crash on CHERI allowing a developer to catch this without KASAN being involved.

[1] http://cheri-cpu.org

Re:C can be memory safe on Saturday June 22, 2024 @05:48PM (#40762500)
CHERI-RISC-V is being standardised [1], Codasip is working on a commercial implementation of CHERI-RISC-V [2], and lowRISC is working on the Sonata project [3] implementing CHERIoT.

The Early performance results from the prototype Morello microarchitecture report [4] predicts the overhead between 1.8% and 3.0%. We don’t know what that overhead would be in production until such a commercial implementation is delivered but we have enough evidence it is worth the effort with the current estimates and given that CHERI can deterministically prevent around 2/3 of memory-safety-related vulnerabilities [5], not to mention benefits of mitigating future unknown vulnerabilities with compartmentalisation.

[1] https://github.com/riscv/riscv-cheri

[2] https://codasip.com/solutions/riscv-processor-safety-securit...

[3] https://www.sunburst-project.org/

[4] https://ctsrd-cheri.github.io/morello-early-performance-resu...

[5] https://msrc.microsoft.com/blog/2020/10/security-analysis-of...

The CHERI ISA does not provide temporal safety features but it allows building temporal safety mechanisms in software. CheriBSD 23.11 includes user-space heap temporal memory safety that is enabled by default [0]. The paper "Cornucopia Reloaded: Load Barriers for CHERI Heap Temporal Safety" at ASPLOS 2024 will describe the current implementation [1].

For embedded systems, the CHERIoT [2] platform implements hardware-assisted temporal memory safety without MMU.

[0] https://ctsrd-cheri.github.io/cheribsd-getting-started/featu...

[1] https://www.asplos-conference.org/asplos2024/main-program/ab...

[2] https://cheriot.org/papers/2023-micro-cheriot-uarch.pdf

Re:Two Stories for "What Is CHERI?" on Friday October 13, 2023 @07:10AM (#37869271)
CHERI is not specific to C/C++ but aims to provide primitives at the hardware level that can be used to make software safer (including programming languages) in terms of (spatial and temporal) memory safety and also to compartmentalize your software stack (e.g., separate third-party software libraries from the core of your application). It is true that the only currently stable CHERI-extended SDKs for programming languages are CHERI LLVM [1] (for CHERI-RISC-V) and LLVM for Morello [2] for CHERI C/C++ [3]. However, there have been more projects that extend other SDKs for CHERI: Rust [4] [5], JavaScriptCore and WebKit [6] [7], OpenJDK [8].

[1] https://github.com/CTSRD-CHERI/llvm-project

[2] https://git.morello-project.org/morello/llvm-project

[3] https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-947.pdf

[4] https://github.com/kent-weak-memory/rust

[5] https://soft-dev.org/events/cheritech22/slides/Cooksey.pdf

[6] https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/cheri...

[7] https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-975.pdf

[8] https://www.dcs.gla.ac.uk/~jsinger/cheritech23_slides/anisbe...

Re:Two Stories for "What Is CHERI?" on Friday October 13, 2023 @06:45AM (#37869096)
"Any UK or international registered business or organisation can request a Morello Board by completing the form below":

https://dsbd.tech/get-involved/morello-board-request/

Alternatively, you can use a Morello board running CheriBSD that is available in the GCC Farm Project:

https://cfarm.tetaneutral.net/news/45