Is nothing sacred any more? Gosh, there's vulnerabilities everywhere. Just when you thought you were safe after updating to protect your CPU, now there's this. Thought RAM vendors had fixed Rowhammer from 2014? Think again, it's back with Half-Double.
Spectre is one in a list of critical vulnerabilities in modern processors that was discovered over the last few years, and it seems it's not been solved yet.
NVIDIA has today revealed a bunch of new vulnerabilities in the GPU drivers that affect both Linux and Windows.
Linux is pretty secure right? Well, like everything else, there are and have been problems. Google is aware of this and they use Linux for a lot and now they're providing funding to help boost Linux security.
Here's something we missed with the latest NVIDIA driver updates - turns out that NVIDIA had multiple security issues that they put out in a recent security bulletin.
This kind of PLATYPUS is not a sweet and unusual mammal, this is a security problem recently announced that affect Intel across server, desktop and laptop CPUs.
VUSec have published and shown an example of a newly discovered flaw present with both Intel and AMD processors when used with Linux.
Users of the popular bootloader may want to update their systems in order to mitigate the danger of this new exploit.
Security? What security? Say hello to 'LVI' (Load Value Injection), a new class of' transient-execution attacks' exploiting flaws in modern processors and it defeats all existing countermeasures.
Thought Intel was the only one? Well you would be living under a rock with all the past issues but Intel seemed to be constantly hit harder, and they had another recently. This time, it's AMD's turn in the security spotlight.
Researchers have uncovered a fun new vulnerability in Intel processors, and this one has a claim attached that it's not possible to fix it.
Intel are not having a good time lately are they? More vulnerabilities in their CPUs have been made public.
Here's your morning dose of uh-oh, a security researcher has made an unfortunate vulnerability in KDE public. Not something we usually cover, but since there's no fix available it's worth letting you know.
Showing 20 to 33 of 33 entries found.