The bibliographic entry was discovered and compiled by a machine, and published without a person checking it against the publication. The publication itself is the authors' own work — this badge says nothing about it.

Capability Hardware Enhanced RISC Instructions: CHERI Instruction-Set Architecture (Version 8)

Where it appeared

Published inCL Technical Reports

Identifiers

DOI10.48456/tr-951
OpenAlexW7213319025

From OpenAlex, which stores abstracts as an index of words and their positions: what is shown is rebuilt from that, and reads fluently whether or not it is what the author wrote.

Abstract

This technical report describes CHERI ISAv8, the eighth version of the CHERI architecture being developed by SRI International and the University of Cambridge. This design captures ten years of research, development, experimentation, refinement, formal analysis, and validation through hardware and software implementation. CHERI introduces an architecture-neutral capability-based protection model, which has been instantiated in various commodity base architectures to give CHERI-MIPS, CHERI-RISC-V, Arm’s prototype Morello architecture, and (sketched) CHERI-x86-64. It enables software to efficiently implement fine-grained memory protection and scalable software compartmentalization, by providing strong, non-probabilistic, efficient mechanisms to support the principles of least privilege and intentional use in the execution of software at multiple levels of abstraction, preventing and mitigating vulnerabilities. Design goals include incremental adoptability from current ISAs and software stacks, low performance overhead for memory protection, significant performance improvements for software compartmentalization, formal grounding, and programmer-friendly underpinnings. CHERI blends traditional paged virtual memory with an in-address-space capability model that includes capability values in registers, capability instructions, and tagged memory to enforce capability integrity. This hybrid approach, inspired by the Capsicum security model, addresses the performance and robustness issues that arise when trying to express more secure programming models, minimising privilege, above conventional architectures that provide only MMU-based protection. CHERI builds on the C-language fat-pointer literature: its capabilities can describe fine-grained regions of memory, and can be substituted for data or code pointers in generated code, protecting data and improving control-flow robustness. Strong capability integrity and monotonicity properties allow CHERI to express a variety of protection idioms, from enforcing valid C-language pointer provenance and bounds checking to implementing the isolation and controlled communication structures required for software compartmentalization. CHERI’s hybrid approach allows incremental adoption of capability-oriented design: critical components can be ported and recompiled to use capabilities throughout, providing fine-grain memory protection, or be largely unmodified but encapsulated in ways that permit only controlled interaction. Potential early deployment scenarios include low-level software Trusted Computing Bases (TCBs) such as separation kernels, hypervisors, and operating-system kernels, userspace TCBs such as language runtimes and web browsers, and particularly high-risk software libraries such as data compression, protocol parsing, and image processing (which are concentrations of both complex and historically vulnerability-prone code exposed to untrustworthy data sources). CHERI ISAv8 is a substantial enhancement to prior ISA versions. Capability compression is now part of the abstract model. Both 32-bit and 64-bit architectural address sizes are supported. Various previously experimental features, such as sentry capabilities and CHERI-RISC-V, are now considered mature. We have defined a number of new temporal memory-safety acceleration features including MMU assistance for a load-side-barrier revocation model. We have added a chapter on practical CHERI microarchitecture. CHERI ISAv8 is synchronized with Arm Morello.

How it got here

How it got hereagent via openalex
Added2026-10-25 21:05 UTC
Not denied bya person 2026-10-29 17:12 UTC

Cite it as

@techreport{watson2020capability,
  title        = {Capability Hardware Enhanced RISC Instructions: CHERI Instruction-Set Architecture (Version 8)},
  author       = {Robert N. M. Watson and Peter G. Neumann and Jonathan Woodruff and Michael Roe and Hesham Almatary and Jonathan Anderson and John Baldwin and Graeme Barnes and David Chisnall and Jessica Clarke and Brooks Davis and Lee Eisen and Nathaniel Wesley Filardo and Richard Grisenthwaite and Alexandre Joannou and Ben Laurie and A. Theodore Markettos and Simon W. Moore and Steven J. Murdoch and Kyndylan Nienhuis and Robert Norton and Alexander Richardson and Peter Rugg and Peter Sewell and Stacey Son and Hongyan Xia},
  year         = {2020},
  journal      = {CL Technical Reports},
  doi          = {10.48456/tr-951},
}

This record lives at https://refs.drheap.org/watson2020capability/ and will keep doing so. It used to be called watson2021capabilityb, and those addresses still resolve to this one.