37-Year-Old Bug Meets Modern Kernel: How OpenBSD Fell to a Chained Exploit

Michael Miller · 2026-10-16

Imagine a flaw so old it predates the web, sitting quietly in a shared-memory routine. Now imagine pairing it with a fresh kernel bug to slip past every modern defense. That's exactly what happened with OpenBSD 7.9, and the lesson matters whether you're running a firewall or an antidetect browser. Security firm Calif published a local privilege escalation exploit that gains root on OpenBSD 7.9. The chain links an integer overflow that's roughly 37 years old with a separate kernel flaw. Together, they bypass KARL kernel-address randomization plus SMAP and SMEP hardware protections. Calif released a full writeup and proof-of-concept code after OpenBSD shipped fixes. ### Why a 37-Year-Old Bug Still Bites Integer overflows in shared memory aren't glamorous. They're the kind of thing you'd assume got stamped out decades ago. But old code has a way of sticking around, especially in kernels where stability trumps spring cleaning. This bug lurked in a shared-memory path, quietly waiting for someone to do the math wrong. The real twist is the chain. On its own, that overflow might not get you far. Pair it with a second kernel flaw, though, and suddenly you're climbing from a local user to root. It's a reminder that modern exploits rarely rely on a single mistake. They're combinations—small weaknesses stacked until the wall cracks. ### The Defenses That Didn't Hold OpenBSD is famous for its security posture. KARL randomizes kernel addresses, and SMAP/SMEP make it harder to execute or access memory across privilege boundaries. Yet the exploit walked right through them. That doesn't mean these protections are useless. It means they're not magic. A clever enough chain can still find a seam. > "Security isn't a destination—it's a constant game of catch-up. The moment you think you're safe, someone finds the crack you missed." For anyone building or using antidetect browsers, this hits close to home. Antidetect tools rely on isolated environments, fingerprint spoofing, and sometimes kernel-level tricks to keep sessions separate. If the underlying OS has a root exploit, those layers can evaporate. A compromised kernel means every browser profile is potentially exposed. ### What This Means for Antidetect Browser Users If you're running antidetect browsers for multi-accounting, ad verification, or privacy, you're already thinking about fingerprints and proxies. But the OS layer matters just as much. A root exploit on the host can undermine even the best browser isolation. That's why patching isn't optional—it's foundational. - **Patch promptly:** OpenBSD already shipped fixes. If you're on 7.9, update now. - **Limit local access:** The exploit requires local access. Keep untrusted users off your systems. - **Layer your defenses:** Combine antidetect browsers with hardened hosts and network segmentation. - **Stay skeptical:** Old bugs don't retire. Audit legacy code paths. Calif's writeup is worth a read if you're into the gritty details. But the headline is simple: a 37-year-old integer overflow just helped someone get root on a modern, security-focused OS. That should make all of us double-check our assumptions—and our patch levels.