
calif.io
October 16, 2026
6 min read
55/100
Summary
Calif disclosed an OpenBSD local privilege-escalation exploit that combines two kernel flaws to obtain a root shell despite KARL, SMAP and SMEP protections. One flaw originates in original BSD code from roughly 37 years ago: a System V shared-memory attachment counter was stored as a signed 16-bit value. Repeated process forks could overflow the counter past 32,767 and wrap it to a negative value, enabling a race condition that produced a use-after-free. The exploit paired that bug with a separate kernel out-of-bounds write. It mapped 127 shared-memory segments, forked 259 processes to wrap the attachment count to -32,643, then used heap grooming and an IPC_RMID race to create a size-confused shared-memory segment. A conditional -1 write modified IP multicast-membership fields, and subsequent socket cleanup altered page-table mappings so user memory became supervisor-accessible. Calif then overwrote a predictable kernel function pointer to execute kernel code and restored it after obtaining root access. OpenBSD addressed the flaws in errata 026 and 018. Calif said OpenBSD's kernel address randomization does not randomize allocator base addresses or allocation order, leaving some early-boot kernel objects predictable on the same hardware. It proposed safe-unlinking checks, randomizing the self-referential page-table mapping, and making kernel allocation less deterministic. Calif also cited compiler-based array-bounds sanitization and forthcoming Alloc Tokens as mitigations for out-of-bounds and heap-exploitation techniques.
Key Takeaways
What the discussion said
The AI angle was a small but revealing side thread rather than the substance of the discussion. One participant claimed the site’s exploit coverage is machine-generated and suggested AI is also discovering vulnerabilities, framing it as an automated analogue to fuzzing. Another gave a more concrete anecdote: directing an AI system at tiny, mature OpenBSD utilities reportedly surfaced several longstanding defects, including a buffer overflow that was probably difficult to weaponize. The implication was not that AI has solved vulnerability research, but that it can cheaply widen the search across old C code where manual review has plainly missed flaws for decades. There was no real evaluation of which model, workflow, or verification process produced those findings, so enthusiasm remained anecdotal. The only unambiguously negative AI reaction concerned presentation: a reader found an AI-generated lead image off-putting before the article had established any technical value. The broader thread focused on OpenBSD’s security reputation and C-language bugs, but those arguments did not materially assess AI systems. Overall, commenters treated AI-assisted bug hunting as plausible and potentially useful, while offering little evidence that generated editorial content or visuals improve the reader experience.
Where opinion split
The narrow dispute is whether AI is becoming a meaningful vulnerability-discovery tool or merely being loosely compared to fuzzing. Supporters point to AI reportedly finding old defects in small, established Unix tools; skeptics have no direct rebuttal, but the discussion provides no reproducible evidence, model details, or proof that AI found bugs humans and conventional analysis would not.
Community Sentiment
Positives
Concerns

Assessing Claude Mythos Preview's cybersecurity capabilities
Apr 7, 2026

Copy Fail – CVE-2026-31431
Apr 29, 2026

Claude Code Found a Linux Vulnerability Hidden for 23 Years
Apr 3, 2026

Exploit brokers pay $500k for WordPress RCEs. I found one with GPT5.6 and $25
Jul 20, 2026

Evaluating and mitigating the growing risk of LLM-discovered 0-days
Feb 5, 2026