The PS5 version of Rockstar Games’ upcoming open-world action-adventure game, GTA VI, now requires firmware version 14.22 to boot.
Twotter/X user PlaystationSize, known for sharing database entries made to PlayStation servers, has revealed that GTA VI on PS5 will have a mandatory requirement of firmware 14.22. In other works, the game will only boot if the console has the aforementioned version, or higher, of its system software installed.
Around a month ago, the Twitter/X user had shared that GTA VI would require at least PS5 firmware update 14.10. However, since then, two additional updates have been rolled out i.e. 14.20 and 14.22. Hackers have been actively investigating potential kernel vulnerabilities firmware 14.00 and 14.10. Among the intended goals is to dump GTA VI game files and run the game day one on PC via PS5 emulation/translation, but the odds of that happening are now significantly lower after the updated firmware requirements.
Known scene developer gezine_dev discovered a kernel exploit for PS5 firmware 14.10, indicating that those who updated past firmware 13.60 may soon be able to jailbreak their consoles. The hacker mentioned that the kernel exploit they used to achieve the firmware 13.xx jailbreak was patched with firmware 14.00. They clarified that their hack is new and not the same as the “relapse” exploit that was originally shared by modders Nathan Fargo and Sonic ISO. As far as reading game files from the console memory is concerned, the scene developer said that the old method for dumping executables doesn’t work on firmware 14.xx and that a hypervisor exploit will be required to gain access to that functionality.
Subsequently, security researcher kuzibelit shared that they discovered an exploit for PS5 firmware version 14.20. They were able to find a userland entry point a few hours after the firmware was released. According to them, Remote Lua Loader is successfully executing payloads live with FTP server when listening on port 1337. They were also able to trigger a repeatable kernel panic (system crash) on the same firmware while testing native userland thread execution via syscall 430 and passing malformed configurations.
