Technology•

A $1.2 Million AI Run Turned Up 948 Linux Kernel Flaws, and Crypto Runs on Linux

OpenAI says its AI found 948 Linux kernel flaws and wrote a working attack for each; crypto security voices say decentralization leaves the industry better placed than most.

Written By :MINRK
A $1.2 Million AI Run Turned Up 948 Linux Kernel Flaws, and Crypto Runs on Linux

Image by Larry Ewing, Simon Budig, Garrett LeSage via Wikimedia Commons (Attribution)

Mentioned in This Article

ETH
ETH
Ethereum
$2,418.93
4.02%

1. OpenAI Linux Flaws Claim: 948 Kernel Bugs, Each With a Working Attack

OpenAI said in a post on X on November 5 that its AI system found 948 flaws in the Linux kernel and wrote a working attack for every one of them, at an average discovery cost of about $1,279 per flaw. The result matters beyond the technology industry because Linux underpins much of global computing, including most blockchain infrastructure. Security figures in crypto say decentralization leaves the sector relatively well placed.

The claim comes from OpenAI itself, and the model behind it has not been released, so outside researchers cannot yet reproduce the work. Even so, the figures illustrate how quickly automated tools are changing the economics of vulnerability research, a field that has traditionally depended on scarce human expertise.

OpenAI did not mention crypto in its announcement. The connection was drawn by security specialists in the industry, who were asked what a large supply of machine-generated attacks against the Linux kernel would mean for networks that hold digital assets.

2. What Did OpenAI Say It Found?

The company said its AI found 948 flaws in the Linux kernel, the core component of the operating system that manages hardware, memory and the programs running on a machine. For each flaw, the system also produced a working attack, which is a stronger result than a simple list of suspected bugs, since a working attack demonstrates that a weakness can actually be used.

According to OpenAI, each flaw cost roughly $1,279 to find. Taken across all 948, that implies a total run cost in the region of $1.2 million, a figure the company itself cited. To put the spending in context, OpenAI compared it with a hypothetical market value for the same bugs, estimated at between $18.9 million and $66.3 million. That range is based on the payouts typically offered at hacking contests such as Pwn2Own, where researchers are rewarded for demonstrating working attacks on widely used software.

The comparison is hypothetical: the company was not describing money that was actually paid for these flaws. Its point was that finding vulnerabilities with an AI system costs far less than those vulnerabilities would be worth if sold or rewarded under conventional programmes. For defenders, the gap shows that the cost of discovery is falling, and for attackers with access to similar tools, it suggests the same economics could apply to them.

3. How Did the Attacks Work?

The flaws allow an attacker who already has limited access to a machine, such as a basic user account, to gain full control of it. Security specialists call this kind of weakness a privilege escalation, because it lifts a low-level foothold into complete administrative power over the system. It is especially important on shared servers and cloud machines, where many users or programs run side by side.

OpenAI said it tested the attacks on a standard Linux desktop with normal security protections enabled. That detail is relevant because modern systems include defences meant to make exploitation harder, and an attack that works only after those safeguards are switched off would carry much less weight. By stating that the protections were active, the company was indicating that the attacks worked against a realistic configuration.

The kernel is the most sensitive part of the operating system. A flaw there can undermine every layer above it, including software that is otherwise well written, which is why weaknesses of this kind attract the highest rewards at hacking competitions.

4. What Is the Step-by-Step Pipeline Behind the Result?

OpenAI described a pipeline that proceeds in stages. The system first scans for risky code, then identifies specific flaws, tests them in a sandbox, checks whether they can be exploited and finally drafts a fix. The sandbox stage means each suspected flaw is tried in an isolated environment rather than being trusted on the model's judgment alone, and the exploitability check filters out weaknesses that look worrying but cannot be turned into an attack.

The inclusion of a drafted fix reflects the defensive framing OpenAI chose for the announcement. A tool that locates a flaw, proves it can be abused and proposes a repair covers the full cycle that security teams normally split between researchers and engineers.

Human researchers review the results before they are reported to the people who maintain Linux. That review step addresses a common problem in automated bug hunting, which is a high volume of low-quality reports that burden the volunteers and companies responsible for the software. According to OpenAI, results go to maintainers only after a person has looked at them.

5. Why Does OpenAI Say the Goal Is Defense?

OpenAI said the aim is defensive: finding weaknesses before hackers do. It also said AI models are effective for securing software, and that defenders should analyze software proactively to make attacks prohibitively expensive.

The logic is that if the cost of finding a flaw is low for everyone, then software owners who do not search for their own flaws will be searching at a disadvantage. A project that scans its code with the strongest available tools can fix problems before they are exploited, while a project that does not leaves the same problems for others to discover. In that sense the announcement is both a demonstration of capability and an argument for adopting such tools early.

The same economics also explain the concern. Because the bugs cost less to find than they would be worth, an attacker with comparable technology has an obvious incentive to use it, which is why finding them first matters so much to defenders.

6. What Does It Mean for Crypto?

Most blockchain infrastructure runs on Linux. Ethereum is one example: about two-thirds of its nodes run on the operating system, according to the node-tracking site ethernodes.org. Exchanges, custody providers, validators and the servers that support wallets and applications commonly use it too, which is why a large batch of new kernel attacks is relevant to the industry even though OpenAI never mentioned it.

The practical risk is the same one that applies to any organisation running Linux servers: an attacker who gets a small foothold on a machine could use a kernel flaw to take it over completely. For a company that operates signing keys or hot wallets on such machines, full control of a server can mean control of the funds those keys protect.

That is the concern behind the question put to security voices in the industry, and their answers were largely reassuring, though not uniformly so.

7. Why Do Crypto Security Voices Say Decentralization Helps?

Mudit Gupta, chief technology officer of Polygon Labs, told CoinDesk that crypto's decentralization makes it inherently resistant to this kind of exploitation. His argument is that a decentralized network does not depend on a single machine or a single software configuration. Infrastructure is diverse and redundant, so a flaw affecting one environment does not necessarily compromise the whole network, and the system can keep running while individual operators patch their machines.

He contrasted that with traditional software, where a single organisation may run one codebase on a small number of systems. In his view, the diversity and redundancy built into blockchain networks make crypto more resilient to bugs than conventional software.

A second view came from Caducus, a blockchain evangelist and security researcher who posts as @chain_linkd on X. Caducus argued that crypto's constant exposure to attacks has already strengthened it, because the prospect of bounties draws attackers in early. A sector that is probed continually, the argument runs, tends to find and correct its weaknesses sooner than one that is rarely tested.

Both arguments describe the network as a whole. They do not claim that every exchange, custodian or application is protected, and individual operators who run unpatched Linux machines would remain exposed in the way any other organisation would.

8. Why the Cost of Finding Flaws Matters

Vulnerability research has historically been limited by the number of skilled people able to read complex code and by the hours that work requires. Bug bounty programmes and hacking contests exist partly because that expertise is expensive, and they put a price on each confirmed weakness that reflects the effort involved.

An automated system that produces working attacks at roughly $1,279 per flaw changes the arithmetic. If similar results can be repeated, the price of discovery falls well below the rewards that are customarily paid, and the limiting factor becomes how quickly defenders can review, report and patch what is found rather than how quickly flaws can be located.

That shift also puts pressure on the volunteers and companies that maintain widely used software such as Linux. A large number of credible reports arriving at once requires triage and repair capacity, which is one reason OpenAI emphasised human review before anything is sent to maintainers. How well the open-source ecosystem absorbs a steady flow of machine-found bugs will help determine whether the technology favours defenders or attackers in practice.

For readers in crypto, the takeaway is practical rather than alarming: the underlying software is the same as everywhere else, and the habits that matter are the familiar ones, namely prompt patching, limited access to machines that handle keys and regular security review.

9. What to Watch Next

The most important open question is verification. The results are OpenAI's own, and the model has not been released, so independent researchers have not been able to test the 948 flaws or the cost figures. Confirmation by the Linux maintainers, who receive the human-reviewed reports, would give the claim more weight.

Defenders can already act on the underlying lesson. OpenAI's message to software owners is that proactive analysis, including AI-assisted scanning, is becoming a practical necessity, and that timely patching of the Linux kernel remains the most direct protection. For crypto operators, that means keeping servers up to date and treating any machine that holds signing keys as a high-value target.

Related Articles

NEWSLETTERS

Don't miss another story.

Subscribe to the MINRK Newsletter today.

Tick the newsletters you want. No selection? You'll get MINRK Headlines.

By signing up, you will receive emails about MINRK products and you agree to our terms of use and privacy policy.

MINRK Daybook

Market analysis for crypto traders and investors.

EVERY WEEKDAY

MINRK for Advisors

Defining crypto, digital assets and the future of finance for financial advisors.

EVERY THURSDAY

MINRK Protocol

Exploring the tech behind crypto one block at a time.

WEEKLY

MINRK Long & Short

A must read for institutions. Insights, news and analysis delivered weekly.

EVERY WEDNESDAY

MINRK Headlines

The biggest crypto news and ideas of the day.

EVERY WEEKDAY

MINRK Policy

Examining the intersection of cryptocurrency and government.

WEEKLY

MINRK Research

Join thousands of readers who rely on MINRK for data-driven insights on the latest digital asset trends.

MONTHLY