linux-kernel - Re: Wake-up from suspend to RAM broken under `retbleed=stuff`

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20230108222728.69350-1-joanbrugueram@gmail.com>
Date:   Sun,  8 Jan 2023 22:27:28 +0000
From:   Joan Bruguera <joanbrugueram@...il.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        linux-kernel@...r.kernel.org, x86@...nel.org,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Wake-up from suspend to RAM broken under `retbleed=stuff`

I can also reproduce it on my Ryzen 5700G (both real and QEMU+KVM).
So it doesn't appear to be Intel or AMD specific.

Perhaps your BIOS/UEFI keeps the value of %gs or it points somewhere
valid after waking from suspend to RAM, and the ones I have don't?
That's a way I can imagine it not crashing on some HW.
If that's the case, you should still be able to reproduce it on QEMU.

Or it's also possible that the QEMU issue is different from the one on
real HW (though unlikely, I think)