OpenBSD is expanding its support by finally being able to apply AMD CPU microcode updates. It was reported that this comes with the latest code, which supports the update with new abilities. OpenBSD ...
AMD and Google's Security Team have disclosed a major microcode vulnerability affecting all AMD EPYC processors built on the Zen 1 through Zen 4 architectures. That means EPYC 7001 (Naples), 7002 ...
AMD has confirmed an unpatched “processor vulnerability” that may require CISOs to isolate their systems or even air gap them until there’s a fix. AMD has had to confirm the existence of a major ...
When AMD finally issued patches for its critical microcode security hole on Monday, it said that the glitch 'could lead to the loss of Secure Encrypted Virtualization protection.' AMD on Monday issued ...
If you needed any further confirmation that AMD's "Granite Ridge" desktop processors sporting the Zen 5 architecture were on their way before long, the latest piece of evidence is an update for the ...
Some patches are already rolling out, but updates for most impacted processors aren’t expected until late 2023. Some patches are already rolling out, but updates for most impacted processors aren’t ...
What just happened? AMD has confirmed a security vulnerability in some of its processors, which was inadvertently revealed through a beta BIOS update from Asus. The flaw, described as a "microcode ...
The current understanding of 'Inception' is that the vulnerability is local, meaning you'd need to download malware containing the exploit for a potential issue. AMD notes that older Ryzen CPU ...
The fine researchers at Google have released the juicy details on EntrySign, the AMD Zen microcode issue we first covered about a month ago. And to give away the punchline: cryptography is hard. It’s ...
TL;DR: AMD disclosed a critical vulnerability, AMD-SB-7055, affecting the RDSEED hardware random number generator on Zen 5 CPUs, causing 16-bit and 32-bit RDSEED instructions to return all zeroes ...
It's not really a Linux problem, but as is so often the case, Linux kernel developers have to clean up after AMD and Intel. It happened again with the chipmakers' latest CPU vulnerabilities: AMD ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results