PS5 Linux lead quits, blaming LLM users who reported the last hypervisor bug to Sony

Hacker behind PS5 Linux steps away

Andy "TheFlow0" Nguyen, the PlayStation hacker leading the effort to run full Linux on the PS5, has quit the project. According to FRVR Blog, which reported the announcement on 16 September, Nguyen said he is "stepping away from the PS5 scene" and ending his work on PS5 Linux.

"After pouring my heart and months of my life into it, including plans to finish PS5 Pro support and release in 2027, it's all down the sink," he wrote, in social media remarks relayed by FRVR Blog.

What the project achieved

Nguyen has spent more than a decade building exploits and homebrew for PlayStation hardware, and FRVR Blog credits him with the first kernel exploit for the PlayStation Vita. The PS5 Linux project was his most recent undertaking: it effectively turned the console into a Linux box comparable to a Steam Machine, with dual-boot support, letting owners run PC games and a full desktop OS on Sony's hardware.

The final release under his stewardship is version 2.5, which supports the original "Phat" and Slim PS5 models on firmware 3.00 through 7.61. Work on newer firmware versions and the PS5 Pro now stops with his departure.

Why he walked away

Nguyen's stated reasons are twofold, and both involve language models. The first is the changing makeup of the scene. "The scene used to be a group of highly talented researchers, but now it is just a bunch of noobs using LLMs and writing hacks they don't understand," he said, according to FRVR Blog, which notes he took to calling the new arrivals "slop kiddies."

The second is more concrete. Per FRVR Blog, Nguyen says AI-assisted participants discovered the last remaining hypervisor bug in the PS5 — a flaw he had found independently some time earlier and was still depending on — and reported it to Sony in exchange for a bounty. He says he asked them to hold off until after the launch of GTA 6, so that players could buy the game and still enjoy Linux on their consoles, and that they agreed before going ahead anyway: "not a day passed and they decided to waste it instead."

With Sony presumably patching the flaw, FRVR Blog reports that progress on PS5 Linux for consoles running newer firmware may have been ruined.

Part of a wider backlash

Nguyen is not the only one pushing back. The same report notes that RPCS3, the well-regarded PlayStation 3 emulator, recently banned contributions from "vibe coding" participants, on the grounds that submitters were offering code they did not actually understand.

That is a small but telling data point in a broader tension. Review capacity is the scarcest resource in volunteer-driven projects, and machine-generated patches consume it disproportionately: they can look plausible while demanding exactly the expert scrutiny that hobbyist maintainers have the least of. In this case the dynamic did more than add review noise — it handed less-skilled participants the means to find, and monetise, a vulnerability the project relied on.

Why it matters

If Nguyen's account is accurate, this is a structural story, not just a burnout story. Language models lowered the skill floor for locating a high-value console bug, and the people who used that capability chose a vendor bounty over the community's roadmap. For reverse-engineering scenes, that changes the economics: the vulnerabilities they depend on are now discoverable — and reportable — by anyone with a chatbot.

The immediate cost falls on users. PS5 Linux ends, for now, at version 2.5, with PS5 Pro support cancelled and consoles on newer firmware likely locked out. The wider signal for open source is that AI-generated code is not merely a moderation nuisance; in the wrong circumstances it can remove a project's technical foundations outright, and bans on "vibe coded" contributions like RPCS3's may become a standard defensive measure.