Latest

Technology

OpenBSD 8.0 adds Intel Arc and three security patches

OpenBSD 8.0 shipped on October 20, 2026 with support for Intel Arc A-Series, 512 GB of kernel space on amd64 and up to 64 vCPUs per guest.

OpenBSD 8.0 adds Intel Arc and three security patches
OpenBSD 8.0 adds Intel Arc and three security patches

Two remote holes in more than thirty years. That is the figure Theo de Raadt repeats with every release and that he wrote again on October 20, 2026, when OpenBSD 8.0 appeared as the project's 61st release. The message to the openbsd-misc list keeps the usual proud phrase and adds, right below it, a novelty that had not been seen in the system's headlines for years: support for Intel Arc A-Series graphics cards, the DG2 family Intel dubbed Alchemist, along with other improvements to this operating system with more than 30 years of history.

The pace has not changed since 1996 either. A release every six months, with no public roadmap or beta versions with fanfare, with the source tree open and anyone who wants to look can look. In this release the announcement brings OpenSSH 10.6, LibreSSL 4.4.0, the new rtrd(8) daemon for validating RPKI routes and 13,060 binary packages already compiled for amd64, according to the official release note.

The easy reading is that OpenBSD is catching up on hardware. The interesting one is different: a system that has spent three decades selling code auditing as its method publishes a version whose most visible change is a GPU, while the work that truly sustains its reputation remains buried in the patches.

A hardware leap you notice on the desktop

Arc A-Series support arrives via inteldrm(4) and it does not come alone. The project updated drm(4) to the state of the Linux 6.18.53 kernel and at the same time raised the kernel's virtual address space on amd64 from 4 GB to 512 GB, according to the project founder's announcement. The two pieces fit because without that margin the kernel cannot map more than 4 GB of VRAM, and the Arc Alchemist start above that figure. The pmap(9) direct map also moves to a random position.

On the remaining platforms, hibernation arrives on arm64 with validations for the blocks copied when unpacking the image, and swap encryption uses the CPU's AES instructions on amd64 and arm64.

Change Before In OpenBSD 8.0
Kernel virtual addresses on amd64 4 GB 512 GB
Multiprocessing in vmm guests No support Up to 64 vCPUs per machine
Intel Arc A-Series (DG2/Alchemist) No support Via inteldrm(4), Linux 6.18.53 drm
Hibernation on arm64 Not available Available, with image validation
loongson architecture Supported Retired, does not compile with Clang 22

In networking there are two notes that affect daily laptop use. The qwz(4) driver adds 802.11n with 40 MHz channels, and PF queues break the 4 Gbps barrier, according to Undeadly 's review of the cycle's changes.

vmm grows to 64 vCPUs and organizes machine ownership

Virtualization takes the other half of the announcement. vmm(4) and vmd(8) now support up to 64 virtual CPUs per guest, x2apic mode for guests, MSI/MSI-X interrupts on virtio devices and checksum offload. These are improvements you notice when running real workloads inside a virtual machine. Welcome improvements, applauded by the system's users.

There are two less flashy changes that explain the project's direction. Each virtual machine's ownership is managed with files, which ties the guest's lifecycle to a descriptor rather than a process. And the elf(5) loaders of vmd(8) no longer read out of bounds with binaries with malformed headers, a classic flaw in hypervisors that accept third-party images.

Emulation also gains pieces underneath, with an ioapic i82093aa and a lapic compatible with i82489dx that fix the boot of 32-bit Linux guests, plus improvements in qcow handling.

The limits remain where they were. vmm(4) requires a CPU with hardware-assisted virtualization and extended or nested paging, as its man page documents, and guests receive a virtual CPU, network interface, disk and serial port. Anyone looking for graphics acceleration inside a virtual machine will not find it here.

pledge and unveil, the part that does not make the headline

The permissions system has been the house signature for a decade. pledge(2) arrived with OpenBSD 5.9 on July 19, 2015 and separates the set of POSIX functions into about three dozen subsystems; if the program declares three and then tries to use a fourth, the process dies with a SIGABRT it cannot catch. unveil(2) appeared on July 13, 2018 with OpenBSD 6.4 and does the same with the file system, since the first call hides the entire tree except the declared paths.

In 8.0 the security harvest is plumbing, not headlines. There is a fix to pledge(2) in vfs(9), an adjustment to the levels and options of pledge_sockopt() for different socket types, and an extension of unveil(2) that now restricts reading and writing of man(1), makewhatis(8) and man.cgi(8). pax(1) stopped extracting malicious files outside the working directory, and iked(8) rejects malformed or out-of-state IKEv2 messages. Undeadly adds that httpd(8) and smtpd(8) are randomly relinked on each boot.

There is the method. Not a heroic patch, but a sum of small fixes reviewed file by file, by an auditing team of between six and twelve people working since the summer of 1996, according to OpenBSD's security page.

The same surface-reduction criterion that mobile projects like GrapheneOS apply to harden a Pixel against tracking is applied here to every system daemon, with the difference that in OpenBSD the permissions list lives in the application's code and not in an external layer.

The cryptographic chain also moves. OpenSSH 10.6 disables the LZ77 dictionary encoder of ssh(1) to prevent a possible side-channel leak and adds experimental support for post-quantum composite signatures mldsa44-ed25519. LibreSSL 4.4.0 cleans up the DTLS code and fixes CRL handling with the same score. While OpenSSL prepares DTLS 1.3, GREASE and AVX512 paths, the OpenBSD stack advances with the handbrake on compatibility.

The routing chapter has a new name, because the project imported rtrd(8) and its control rtrctl(8) for the RPKI-To-Router protocol, and bgpd(8) incorporated the RTR v2 error codes from the IETF draft known as 8210bis.

The limits the track record does not cover

The 8.0 errata page had four patches on the same October 20. Three are security: an update of nsd(8) to version 4.15.3 that carries four CVEs, several video(4) flaws that could cause use-after-free and kernel memory corruption, and a heap overflow that the advisory describes as remotely triggerable. The latter deserves precision, because it only affects amd64 with AES-NI and octeon with a cryptographic coprocessor, and only with IPsec and AES-GMAC. AES-GCM is not affected.

That nuance matters for reading the two remote holes phrase. The figure refers to the default installation over more than thirty years, not to code without flaws, and that IPsec configuration is not enabled out of the box.

In hardware the progress comes with a date. The 8.0 notes mention only the Arc A series, the DG2 from 2022, so support appears four years late. Loongson disappears because it stopped compiling with Clang 22, and sparc64 changed tooling.

The desktop exists, with Firefox 157 and LibreOffice 26.8 among the packages, but the official binary count leaves two architectures with the figure unpublished, which means there you have to compile from ports. The update tools also received their share of hardening: fw_update(8) verifies the signature of the local SHA256.sig before trusting it, and pkg_add(1) stopped searching the current directory.

What OpenBSD still teaches Linux

The comparison with Linux is usually framed badly, as a contest between two kernels. The difference lies in who answers for the code: Linux spreads review among subsystem maintainers and distributions, while OpenBSD keeps a team of auditors who read file by file what is going to enter the tree. For those who administer servers, the five cybersecurity tools for Linux worth mastering remain the starting list when reviewing a freshly installed machine.

The project's most valuable asset has never been in its own operating system. OpenSSH, born in OpenBSD, is the example the project itself gives of the effect it has had outside the house, and several of the techniques on its list of innovations, from W^X to privilege separation, have become common vocabulary in other systems. The paradox of 8.0 is that the release is remembered for a GPU and not for the plumbing work. It remains to be seen whether the release six months from now keeps the pace or returns to the silence of small patches, because the system that promises two remote holes in three decades is still alive thanks to each release devoting more lines to closing doors than to opening windows.

José Maldonado

Author

José Maldonado

Activist and blogger on technology, free software and blockchain.

The latest
From Huang to Botín, from Zara to Byron: corporate responsibility in global capitalism

Keep reading