3 ms·
AMD fix status: https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7014.html https://www.amd.com/en/resources/product-security/bulletin/a... htt
by pella 2y ago
AMD fix status: https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7014.html https://www.amd.com/en/resources/product-security/bulletin/a...
https://ubuntu.com/security/CVE-2023-31315 https://ubuntu.com/security/CVE-2023-31315
- edelbitter 2y ago> Please refer to your OEM for the BIOS update specific to your product. Unless running hardware also used by powerful hosting providers (some of which care for security), these mitigation will not reach many systems. Checked a few "client" samples, seems like MSI has provided updated binary blobs, ASRock has provided some, Gigabyte has provided broken ones first and then backdated the new ones, ASUS (ROG/RUF/CSM) and Biostar customers are still waiting.
- aftbit 2y agoSo wait, is this fixed in BIOS or microcode? https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit?id=091bd5adf19c7ab01214c64689952acb4833b21d https://git.kernel.org/pub/scm/linux/kernel/git/firmware/lin...
- yencabulator 2y agoBased on my reading of https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7014.html https://www.amd.com/en/resources/product-security/bulletin/a... there's a microcode fix for EPYC generations 1-4 that requires no downtime, everything else needs a firmware update.