Following the 9.00 PS4 WebKit Exploit / 4.03 PS5 WebKit Exploit, Full Chain Exploit Rumored and Root PS5 Keys Obtained yesterday Twitter lit up once again with various PS4 Scene / PS5 Scene developers taking interest after Mark Ermolov's Intel Processor Advisory disclosure of a non-damaging way to extract the security fuses (Chipset + EPID root keys) from the Intel platforms proceeded by Volodymyr Pikhur's AMD Server Vulnerabilities for November 2021 security bulletin. 
For those unfamiliar with Volodymyr Pikhur (aka VPikhur)'s past contributions in the PlayStation 4 Scene, some highlights include being credited for PS4 Southbridge Processor work with EAP / EMC (PS5 EMC UART Pinouts) via side-channel analysis, glitching and ROM recovery in his PS4 IPL AES + HMAC Key Recovery project, a PS4 Presentation at Recon Brussels 2018 (PS4 Rest Mode REcon Slideshow PDF) discussing the custom PS4 Southbridge silicon's security failures and sharing PS4 APU Floor Plan High-Resolution Die Shots (following PS4 Syscon High-Res Images and prior to the PS5 SoC / APU / SSD-Controller Die-Shots) at Toorcon 2019 with speculation his way by ChappaYuan as a potential source of the leaked 7.0 PS4 Decrypted Filesystem and Kernel dump.
While there's currently no definitive consensus among PS5Scene devs publicly on whether the SMAP Bypass FreeBSD 12 Vulnerability May Affect PS5 or the Potential AMD SP (Secure Processor) Glitch for PS5 Fuses reported earlier this year, in mid-August some BIOS SUITE / HDT Serials for AMD Tools leaked but unfortunately an AMD login is required to fully unlock them.
As for consensus among PS4Scene devs, based primarily on Tweets embedded in previous SAMU-related topics it's fairly safe to surmise there are two distinctive groups- those with access to SAMU goodies and those without access... as the latter hopes these newfound AMD vulnerabilities may help level the playing field. If only both groups collectively worked together...
I've recently been pointed to the first article from 2016 linked above by others a few times now, as apparently the Coreboot repository linked there has been updated over the last year or so quietly revealing SAMU's secrets. 
Could info some are seeking have been hidden in plain sight all this time? That wouldn't surprise me any more than the oh-so-predictable Tweet directly below:
For those unfamiliar with Volodymyr Pikhur (aka VPikhur)'s past contributions in the PlayStation 4 Scene, some highlights include being credited for PS4 Southbridge Processor work with EAP / EMC (PS5 EMC UART Pinouts) via side-channel analysis, glitching and ROM recovery in his PS4 IPL AES + HMAC Key Recovery project, a PS4 Presentation at Recon Brussels 2018 (PS4 Rest Mode REcon Slideshow PDF) discussing the custom PS4 Southbridge silicon's security failures and sharing PS4 APU Floor Plan High-Resolution Die Shots (following PS4 Syscon High-Res Images and prior to the PS5 SoC / APU / SSD-Controller Die-Shots) at Toorcon 2019 with speculation his way by ChappaYuan as a potential source of the leaked 7.0 PS4 Decrypted Filesystem and Kernel dump.
While there's currently no definitive consensus among PS5Scene devs publicly on whether the SMAP Bypass FreeBSD 12 Vulnerability May Affect PS5 or the Potential AMD SP (Secure Processor) Glitch for PS5 Fuses reported earlier this year, in mid-August some BIOS SUITE / HDT Serials for AMD Tools leaked but unfortunately an AMD login is required to fully unlock them.
As for consensus among PS4Scene devs, based primarily on Tweets embedded in previous SAMU-related topics it's fairly safe to surmise there are two distinctive groups- those with access to SAMU goodies and those without access... as the latter hopes these newfound AMD vulnerabilities may help level the playing field. If only both groups collectively worked together...
- PS4 SAMU Encryption Info Spotted in CoreBoot GIT
- SAMU on PS4 Reportedly Decrypted by PlayStation 4 Devs
- PS4 Secure Asset Management Unit (SAMU) Processor
I've recently been pointed to the first article from 2016 linked above by others a few times now, as apparently the Coreboot repository linked there has been updated over the last year or so quietly revealing SAMU's secrets. Could info some are seeking have been hidden in plain sight all this time? That wouldn't surprise me any more than the oh-so-predictable Tweet directly below:
