How Someone Just Hacked the PS5 to Run Linux—and Why Sony Will Fight Back

Andy Nguyen has released PS5-Linux on GitHub, a working exploit that can turn original PlayStation 5 consoles into Linux computers—but only on older firmware versions 3.xx and 4.xx. This is the first time anyone has successfully installed Linux that persists across reboots on Sony's current console, breaking through security layers that have kept the PS5 locked down since its 2020 launch.

The hack works by finding and exploiting security weaknesses in older PS5 firmware. Videocardz confirmed it only functions on those early firmware versions, which means the only consoles at risk are ones that either never connected to the internet, or whose owners deliberately turned off automatic updates. The moment Sony patched those vulnerabilities, new consoles became immune.

What the Hack Does (and Doesn't)

Once installed, Linux runs with full control of the PS5's hardware—including its custom GPU (an AMD RDNA 2 chip) and all 16GB of the console's high-speed memory. This means you could run any Linux application, play older console games through emulation, write custom software, or use the PS5 as a general-purpose Linux machine instead of a gaming device.

The catch: installing it requires deep technical knowledge of how the console's security works. You can't just download a tool and run it. You need to understand the layers of security the PS5 uses—the hypervisor (the layer that controls what software can run), the kernel (the core of the operating system), and the bootloader (the code that runs first when the console starts). You have to disable signature verification on each layer, which is a bit like manually unlocking every door in a security system one at a time.

The hack only works on the original, larger PS5 model—what gamers call the "PS5 Phat." The newer, slimmer PS5 has additional security measures that block this attack.

A Pattern Sony Knows Well

This is not the first time we have seen this play out. Sony has fought console modifications for decades, and the PS5-Linux release follows a script that began years ago.

The clearest example came with the PlayStation 3. Sony originally let the PS3 run a full Linux operating system alongside games—a feature called "Other OS." The company even launched PlayStation-edu in 2008, which gave universities free access to PS2 and PSP development kits for research. But in March 2010, Sony removed the Other OS feature via a firmware update, saying it had to be done for security reasons.

The homebrew community did not take this quietly. A hacker named George Hotz published a PS3 jailbreak, and Sony sued him in federal court. The case made headlines. It was settled in 2011, with Hotz agreeing not to distribute the exploit, and Sony established a firm legal precedent: the company would defend its control over the console aggressively.

That pattern has held steady. With the PS5, Sony has not given an inch. The question now is whether the same cycle will repeat.

Why the PS5 Is Much Harder to Hack

The PS5 is Sony's most heavily secured console ever. It uses multiple layers of verification to prevent unauthorized code from running: verified boot (checks that each part of the system is authentic before it runs), hardware-backed attestation (using a special chip to prove the system is legitimate), and isolation between different parts of the system. Breaking in requires bypassing AMD's Platform Security Processor, Sony's custom secure boot, and memory protection in the kernel.

The fundamental vulnerability here is that offline consoles are harder to defend. Sony's security model depends on the console connecting to the internet and installing updates automatically. If your PS5 is offline and running old firmware, you are running code Sony has publicly admitted is insecure. The earlier the firmware, the more vulnerabilities exist to exploit.

One practical limit on how widespread this hack becomes: you need the exact right combination of hardware and firmware. Unlike some older console hacks that could be installed through a simple software download, the PS5-Linux exploit requires matching your specific console revision to compatible firmware. This narrows the addressable user base to early adopters who consciously avoided updates—a relatively small group.

What Happens Now

The broader context here is that this release likely puts Sony on notice to accelerate security patching. The company's pattern across decades suggests it will move quickly to patch the underlying vulnerabilities and potentially redesign future consoles to close off this entire class of attack.

For the modding community, the publish code offers valuable information about how Sony's security actually works and provides a foundation for researching the PS5 further. It may reveal other weak points that could be exploited in later firmware versions.

In this author's view, what is worth flagging is the enduring tension this reveals. Console makers invest enormous resources in preventing unauthorized code execution. The hacking community invests just as much effort in finding ways around those controls. Neither side has ever won permanently. We have seen this pattern before, when the Xbox, the Nintendo Switch, and earlier PlayStations all went through the same cycle of lockdown, exploit, legal action, and repeat. The PS5-Linux release suggests the same cycle is now underway with Sony's current generation. Sony will patch, the modding community will look for new vulnerabilities, and the cycle continues.

What drives that persistence? For many enthusiasts and researchers, it is simply the principle—the desire to have full control over hardware they own. For others, it is practical: they want to build tools, run emulators, or repurpose aging hardware rather than retire it. And for some, the appeal is the intellectual challenge itself. None of that has changed in thirty years, and nothing suggests it will.