AIToday
AI Coding AssistantsAI Safety & AlignmentOpenAI BlogPublished: Nov 5, 2026, 10:00 JST

OpenAI pipeline finds 948 Linux kernel LPEs for $1,213,430

Send on LINE
OpenAI pipeline finds 948 Linux kernel LPEs for $1,213,430

3 Key Points

  1. What happened

    OpenAI said its five-stage pipeline, built on an upcoming cyber model, scanned the latest Linux kernel in mid-October 2026 and produced 948 unique local privilege escalation exploits for $1,213,430 in API credits, far above the 166 found in late July 2026 by GPT‑5.6 Sol.

  2. Why it matters

    The same pipeline plus a stronger model found roughly 5.7 times as many distinct exploits as the July run, which OpenAI says shows defenders should rescan already-audited code as model capabilities improve.

WHO IT HITSOpen-source maintainers and enterprise security teams running Linux-based systems now face a faster flow of machine-generated vulnerability reports; OpenAI says 61 LPEs had been patched upstream and 43 had staging patches by the end of its scan.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

OpenAI frames this work as part of Patch the Planet, a Daybreak initiative, and says its broader aim is to help defenders find and fix vulnerabilities before attackers use them. The pipeline's five stages are designed to move from scanning code to reporting vulnerabilities with candidate patches, which the maintainers can review. By building the prototype around an upcoming cyber model and comparing it with an earlier GPT‑5.6 Sol run, OpenAI is trying to show how quickly a stronger base model can change the economics of finding flaws in a codebase the size of Linux.

The research also yielded a set of operational lessons that go beyond the headline exploit count. OpenAI says the Linux maintainers moved quickly: when the scan and manual analysis finished after 10 days, 61 local privilege escalation issues had already been patched upstream, 43 had staging patches, and 299 were being reported and discussed publicly. It recommends revalidating findings against the latest code to avoid duplicate or obsolete reports, since patches can land while a scan is still running. On the exploitation side, OpenAI found its agents employed 10 techniques that kernel exploitation experts had not seen before, and it noted that human review caught 20 exploits that had actually used a different 0-day vulnerability than the one assigned.

Cost data underpins the argument for proactive scanning. OpenAI says the pipeline was net profitable at the time of the research when measured against historical bug bounty payouts: applying Pwn2Own and TyphoonPWN bounty amounts to the 948 exploits produces a hypothetical valuation range roughly 16 to 55 times the pipeline's cost. It also reports that a kernelCTF campaign producing 21 local privilege escalation exploits cost about $32,936 and could have led to around a $1.5M bounty award, approximately 45 times the cost. OpenAI cautions that the reported costs are more of an upper bound, since better harness engineering could reduce spending at each stage, and that its focus was methodology and measuring model capability rather than cost.

FAQ
How did OpenAI's pipeline process the Linux kernel?
It uses five stages: vulnerability discovery, dynamic validation, exploitability assessment, patch generation, and human review. The discovery stage identified 5,034 audit targets covering about 2.8 million lines of code, roughly 7% of the kernel.
How expensive was it to develop one exploit?
Successful exploits cost an average of $359 in API credits to develop, while unsuccessful exploitation attempts cost $3,922 per case across 69 cases.
What did OpenAI find when it ran the pipeline against Google's kernelCTF environment?
It obtained 25 information leak proofs of concept and 21 local privilege escalation exploits, at roughly $32,936 in API credits, and the campaign lasted 112 hours.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleWarren Renews Breakup Push on UnitedHealth After Amedisys Deal