I’m guessing this is indirect proof that the claims the CIA infiltrated Silicon Valley as a means of infiltrating John Q Public are true and perhaps this “revelation” is a result of some swamp draining. OR is it a bold move by the Silicon sellouts to FILL the swamp?:/
How is it that they can all have the same type vulnerability? It all seems very suspicious to say the least.
Yes its called a back door and they all have it. Probably more than one.
So what is the shared code/architecture?
Not trying to change the subject, but doesn't anyone edit their work any more?
Without Trump in office, against the odds of him ever getting there, we wouldn’t be finding out about this “vulnerability.” This kind of intrusion is CIA based and they do want him dead or otherwise out of office so this plan of theirs can continue. I for one pray to God often for the continued survival of Pres. Trump, his family, the military, and any others currently pushing back against the deep state.
https://www.amd.com/en/corporate/speculative-execution
An Update on AMD Processor Security | AMD
There has been recent press coverage regarding a potential security issue related to modern microprocessors and speculative execution. Information security is a priority at AMD, and our security architects follow the technology ecosystem closely for new threats.
It is important to understand how the speculative execution vulnerability described in the research relates to AMD products, but please keep in mind the following:
The research described was performed in a controlled, dedicated lab environment by a highly knowledgeable team with detailed, non-public information about the processors targeted.
The described threat has not been seen in the public domain.
When AMD learned that researchers had discovered a new CPU attack targeting the speculative execution functionality used by multiple chip companies products, we immediately engaged across the ecosystem to address the teams findings.
The research team identified three variants within the speculative execution research. The below grid details the specific variants detailed in the research and the AMD response details.
Variant / AMD Response Matrix
Google Project Zero (GPZ) Research Title Details
Variant One Bounds Check Bypass Resolved by software / OS updates to be made available by system vendors and manufacturers. Negligible performance impact expected.
Variant Two Branch Target Injection Differences in AMD architecture mean there is a near zero risk of exploitation of this variant. Vulnerability to Variant 2 has not been demonstrated on AMD processors to date.
Variant Three Rogue Data Cache Load Zero AMD vulnerability due to AMD architecture differences.
(Whatever all that means!)