AMD PSP reverse engineering, emulator and vulnerability research https://git.sl0p.foo/amd-psp-re.git/atom/hw/gbr_ih_set.py?h=main 2026-09-30T02:11:06Z 2026-09-30T02:11:06Z user user@clank 2026-09-30T02:11:06Z urn:sha1:db3867ff175ef65a5583fd4b234ee8a30d7721c2 Ring creation rejects a base inside the trusted region with a distinct status, and the interrupt-ring setter is the sibling path that points the processor at a host-supplied ring which hardware writes into, taking its address from the same register pair, so the question was whether that path carries the same check. Every case returns the same error, including the valid address, so the path rejects everything and is not functional in this configuration. The comparison therefore cannot be made and the result is recorded as vacuous on the question asked, explicitly not as evidence that the check is present. Writing a row claiming the path validates its address would have repeated an earlier mistake where a detector's negative control never engaged. What can be said is that the identifier is harmless, since the processor stays usable in all four cases, consistent with the control-space sweep.