News Posts matching #OpenBSD

Return to Keyword Browsing

RISC-V Ecosystem Gets More Standardization as Ubuntu Drops Non-Compliant CPUs

Canonical, the company behind Ubuntu, has announced that its next-generation release will require RISC-V processors to meet the newly ratified RVA23 profile. This specification, approved back in April, includes full support for Vector Instructions 1.0 and a Hypervisor extension. As Laurine Kirk, security researcher at Google, notes, by setting this higher baseline, Ubuntu 26.04 will no longer run on roughly 90% of existing RISC-V single-board computers, including the popular Raspberry Pi-style boards, unless their hardware is upgraded. Canonical's move puts it in step with Google and Microsoft, both of which have already targeted RVA23 for their RISC-V builds. This change will drive manufacturers to ship more secure, future-proof silicon, helping to guard against exploits like GhostWrite, a memory-access vulnerability discovered last year in T-Head's XuanTie C910 CPUs.

We discussed RISC-V ecosystem fragmentation with Andrea Gallo, then the CTO and now the CEO of the RISC-V Foundation, regarding the fragmentation within the RISC-V ecosystem. "If you want to claim that you are RISC-V compatible, then there's an architecture compatibility test suite that verifies that you are complying with the ISA. We run the same tests on a golden reference model and compare the signatures of the tests to ensure alignment with the specification." He added that "We just ratified the RVA23 Profile. The newly ratified RVA23 Profile is a major release for the RISC-V software ecosystem and will help accelerate widespread implementation among toolchains and operating systems." For anyone who wants to ship a working RISC-V processor, be it data center or mobile, the RVA23 profile is the one that guarantees no fragmentation and compatibility.

OpenBSD Turns Off Hyper-Threading to Combat Intel CPU Security Issues

Lead developer for OpenBSD Mark Kettenis has announced that OpenBSD will no longer enable Hyper-Threading on Intel processors by default. This move is intended to mitigate security exploits from the Spectre ecosystem as well as TLB and cache timing attacks, because important processor resources are no longer shared between threads. Their suspicion is that some of the unreleased (or yet unknown) attacks can be stopped using this approach.

This move is supported by the fact that most newer motherboards no longer provide an option to disable Hyper-Threading via BIOS. OpenBSD users who still want to use Hyper-Threading can manually enable support for it using the sysctl hw.smt. The developers are also looking into expanding this feature to other CPUs from other vendors, should they be affected, too.
Return to Keyword Browsing
Nov 16th, 2026 04:44 CST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts