22 Oct 2026 · 0.13.0
AriCodeOS 0.13: DMA memory that cannot leak
The version that closed the last high-priority defect: DMA memory can no longer pass from one protection domain to another, whether a buffer is unmapped, a driver dies or a device completes a request late. One architecture decision and two incidents closed, each fix reproduced before it was changed, audited by independent reviewers and verified on the reference laptop.
What changed
- DMA buffer lifetime (incident 0004, ADR 0038): a process that maps a DMA buffer keeps it alive, so its memory is never handed to anyone else while it is still mapped
- A new mmio_unmap system call (ABI 5); freed address ranges are reused, and a mapping that fails halfway is rolled back
- Mapped DMA memory counts against the quota of the process that maps it; system services without a quota are bounded by an 8-entry buffer cache
- When a driver dies, the kernel stops its device’s bus mastering before freeing its memory, and a restarted driver turns it back on only after resetting the device
- Function Level Reset for devices that advertise it (pci.flr=off disables it), and quarantine for the memory of a device that will not stop
- Buffers a device may still own (incident 0017): after a failed request, virtio-blk keeps the buffer until it has reset the device and then recovers; the USB drivers release it only when the controller confirms
- Three rounds of independent audit for incident 0004, each finding fixed with its own test
- Verified on the laptop with versions 9 and 10 from a production-signed index: every driver enables bus mastering itself after its reset, with no fault event