Researcher Discloses AI-Assisted Linux Root Exploit

The vulnerable path involves shared traffic-control action objects tracked in a per-network-namespace action identifier registry. STAR Labs' analysis identifies tcf_idr_check_alloc() as a relevant lookup path: it reads an action object under a read-copy-update, or RCU, read lock. A concurrent deletion path can free that object without waiting for existing RCU readers, producing a use-after-free condition.

The published proof of concept triggers the race through traffic-control netlink operations, including concurrent filter creation and deletion. The Hacker News reports that the exploit requires unprivileged user namespaces, CONFIG_NET_ACT_GACT, and CONFIG_NET_CLS_FLOWER. It also depends on a kernel-specific return-oriented programming chain with hardcoded offsets, constraints that limit portability across kernel builds.

GBHackers reports that the exploit uses a separate user namespace, where the process can obtain CAP_NET_ADMIN, to access traffic-control operations that would normally require network-administration privileges in the initial namespace. Its account also describes a narrow timing requirement: freed memory must be reclaimed with attacker-controlled data before the kernel validates and increments the object's reference count.

Lee wrote that AI assisted with bug discovery, a Kernel Address Sanitizer proof of concept, and optimization of the race window. In the STAR Labs post, he also cautioned that the systems used had "many blind spots and lapses in reasoning ability" and that human judgment remained necessary during the work.

The disclosure does not identify the model, service, prompts, or interaction history used in the research. As The Hacker News noted, those omissions make it difficult to independently assess how much of the finding or exploit engineering came from the AI system versus the researcher's direction and validation.

For security engineers, the more immediate issue is that full exploit source is public. In comparable kernel disclosures, public proof-of-concept code commonly shifts defensive work from theoretical exposure assessment to testing the kernel packages actually deployed, particularly where user namespaces are enabled.

The Hacker News reports that the upstream fix landed on June 1 and has been backported to several stable branches. It lists fixed releases as:

• •5.10.259
• •5.15.210
• •6.1.176
• •6.6.143
• •6.12.94
• •6.18.36
• •7.0.13

The mainline correction entered 7.1-rc7, according to the same report. Administrators should verify their distribution's kernel advisory and package changelog rather than relying only on an upstream version string, because distributions can backport fixes without changing to the listed release line.

The Hacker News reported no official evidence of exploitation in the wild as of July 28. The disclosed prerequisites mean hardened systems that disable unprivileged user namespaces or lack the needed traffic-control features may not meet the demonstrated exploit conditions, but patch deployment remains the primary remediation.