AMD Doubles Down on Previous Spectre and Meltdown Statments

FrgMstr

Just Plain Mean
Staff member
Joined
May 18, 1997
Messages
55,596
Undoubtedly there has been some loose talk about Meltdown and Spectre and its impacts on AMD CPUs. AMD just sent this over as it wants to be perfectly clear on its position on these threats.

We have seen some initial stories with a couple of inaccuracies so want to make sure we are being perfectly clear.

* There is no change to AMD’s position on our susceptibility to GPZ Variant 1 or GPZ Variant 2 (collectively called Spectre in many news reports).
* The update in relation to Variant 2 is that even though Variant 2 has not been demonstrated to work on AMD products due to differences in our micro architecture, out of an abundance of caution we are making optional micro code updates available to further contain the threat.

Again, to make it perfectly clear we have not changed our statement erlated to our susceptibility to Variant 2. Let me know if you have questions or need additional details.




These are Mark Papermaster's previous statements to refresh your memory.


An Update on AMD Processor Security

The public disclosure on January 3rd that multiple research teams had discovered security issues related to how modern microprocessors handle speculative execution has brought to the forefront the constant vigilance needed to protect and secure data. These threats seek to circumvent the microprocessor architecture controls that preserve secure data.

At AMD, security is our top priority and we are continually working to ensure the safety of our users as new risks arise. As a part of that vigilance, I wanted to update the community on our actions to address the situation.
** Google Project Zero (GPZ) Variant 1 (Bounds Check Bypass or Spectre) is applicable to AMD processors.
* We believe this threat can be contained with an operating system (OS) patch and we have been working with OS providers to address this issue.
* Microsoft is distributing patches for the majority of AMD systems now. We are working closely with them to correct an issue that paused the distribution of patches for some older AMD processors (AMD Opteron, Athlon and AMD Turion X2 Ultra families) earlier this week. We expect this issue to be corrected shortly and Microsoft should resume updates for these older processors by next week. For the latest details, please see Microsoft’s website.
* Linux vendors are also rolling out patches across AMD products now.
** GPZ Variant 2 (Branch Target Injection or Spectre) is applicable to AMD processors.
*While we believe that AMD’s processor architectures make it difficult to exploit Variant 2, we continue to work closely with the industry on this threat. We have defined additional steps through a combination of processor microcode updates and OS patches that we will make available to AMD customers and partners to further mitigate the threat.
* AMD will make optional microcode updates available to our customers and partners for Ryzen and EPYC processors starting this week. We expect to make updates available for our previous generation products over the coming weeks. These software updates will be provided by system providers and OS vendors; please check with your supplier for the latest information on the available option for your configuration and requirements.
*Linux vendors have begun to roll out OS patches for AMD systems, and we are working closely with Microsoft on the timing for distributing their patches. We are also engaging closely with the Linux community on development of “return trampoline” (Retpoline) software mitigations.
** GPZ Variant 3 (Rogue Data Cache Load or Meltdown) is not applicable to AMD processors.
* We believe AMD processors are not susceptible due to our use of privilege level protections within paging architecture and no mitigation is required.

There have also been questions about GPU architectures. AMD Radeon GPU architectures do not use speculative execution and thus are not susceptible to these threats.

We will provide further updates as appropriate on this site as AMD and the industry continue our collaborative work to develop mitigation solutions to protect users from these latest security threats.

Mark Papermaster,
Senior Vice President and Chief Technology Officer


Discussion
 
So will Windows 10 determine that you have an AMD processor and not load its update? Thought not. :confused:
 
So will Windows 10 determine that you have an AMD processor and not load its update? Thought not. :confused:
And if you're running an incompatible anti-vir program it will go ahead and reboot your system without warning so the bricking can commence even moar faster.
 
So will Windows 10 determine that you have an AMD processor and not load its update? Thought not. :confused:
Actually it can. Assuming MS doesn't screw something up. Software can always check the CPU type.

Also AMD, Intel, MS, and all the OEM's know that people rarely update their BIOS's so Intel/AMD provide means for the OS (can be Windows, Linux, whatever) to load updated microcode for the CPU after the PC finishes booting and the BIOS hands off control to the OS. They've been doing that for years if not decades now.

By installing the latest BIOS yourself though the OS won't have to do that and have more security/performance (either can happen with new microcode) during the boot process too so its still a good idea to always update your BIOS.
 
So will Windows 10 determine that you have an AMD processor and not load its update? Thought not. :confused:

Huh? AMD just said that there is an impact here on AMD processors and that they are working with Linux developers, not just Microsoft.
 
Susceptible to spectre, just like every other modern cpu including arm, spectre is waaaaaaaaaay harder to use and is "slower", still yeah they are patching it.

Meltdown is the biggie in every way, threat wise and performance wise, this is a problem for Intel and some models of ARM processors.
 
Well the good news is that the 9700K and 2nd Gen Zen CPU's should be free of all of these issues regardless is good enough for me.

Main media never gets anything right.

Anytime there is a settlement/fine to someone/corporation, I swear, one news outlet has it at 50 million, the other, 30 million. You can find these types of discrepancies all over the news outlets if you pay attention.

The media does this with all their data.

Glad to see AMD making the effort to keep the record straight.
 
Huh? AMD just said that there is an impact here on AMD processors and that they are working with Linux developers, not just Microsoft.

what he meant was that windows ignores the cpu code(which is part of the mandatory statistics sent back to microsoft so there's no excuse for that) and downloads and installs the patch no matter what processor you have thus the issue amd athlon 64's ran into.. either way the problem is microsofts half ass lazy coding they've always been known for.
 
So they don’t have the problem but they’re issuing a performance hindering fix for the non-problem?
 
Well the good news is that the 9700K and 2nd Gen Zen CPU's should be free of all of these issues regardless is good enough for me.

I doubt you see a CPU free of this the next decade. The current only solution is to use slower in order designs that rely more on compilers. And the only known performance CPU in this area is Itanium.
 
So they don’t have the problem but they’re issuing a performance hindering fix for the non-problem?

Windows does not apply patches to kernal with any brand in mind, it is blanket so what they patch will apply to Intel and AMD equally, MS don't actually care how it affects each system.
 
Windows does not apply patches to kernal with any brand in mind, it is blanket so what they patch will apply to Intel and AMD equally, MS don't actually care how it affects each system.

The OS patch is just one of 2 components needed. Microcode is the second and now AMD is funny enough supplying this. So then you can retest Zen systems etc and see what performance impact is there. But waiting as long as possible and call it optional makes 3rd party benching of it less likely within the newsworthy timeframe.
 
The Windows patch is just one of 2 components needed. Microcode is the second and now AMD is funny enough supplying this.

AMD has been running microcodes updates since March 2 2017, kind of not really a surprise.
 
To fix an issue they claim isn´t there? Sure...hahahaha!

Last I saw it was maybe it can happen but we are confident it is unlikely, kind of the reason why there are no Zen reviews on the subject, and it is not like you can't just buy one an test it out either. the lack of articles on it seem to suggest that AMD are pretty confident with their position.
 
So they are supplying fixed microcode, yet claims not affected. Good PR joke AMD :D

Every single OOO CPU is hit, no exception. And more to come in the future.


Are you not on earth? Do you also fall prey to manipulation and fake news like most?

AMD never said that they are immune to Variant 2, they said that there are a near zero chance of exploiting it and that it has not been shown on AMD CPU's. This is still the case and nothing has changed on that statement.

They are doing the logical thing to do. Near zero is not zero, so patch it anyway before someone finds a way to exploit it. Spectre does not have the same performance issues as Meltdown, that the real problem for performance.

Since you know the performance impact that this patch has on AMD CPU's, please share it with us...
 
To fix an issue they claim isn´t there? Sure...hahahaha!

Seriously. Please listen to yourself. Please show me where AMD said that their CPU's are 100% unaffected by variant 2? Maybe I missed them saying that. They said near zero. Is near zero, zero? They are just patching that might be an issue in the future and is not taking chances. For now it is not an issue, but who knows what might happen in the future.
 
So they are supplying fixed microcode, yet claims not affected. Good PR joke AMD :D

Every single OOO CPU is hit, no exception. And more to come in the future.

Another ignorant person. Please show me where AMD said that their CPU's are 100% not affected. Do you know what near zero means? It does not mean 100%, does it? Seriously...

They still hold to the point that it is near zero, so how has this changed?
 
So they don’t have the problem but they’re issuing a performance hindering fix for the non-problem?
Since you are so wise, please show us the benchmarks of this. I am not saying it will not make an impact, but we know Meltdown is the real problem, in which AMD is not affected. If your car has a .001% chance of exploding and there is a fix to prevent it, would you apply it?

So if AMD said that their CPU's have a near zero chance of being hacked and they then decide to patch it, they are being dishonest? From where are you really? Do you work for Intel?
 
So they don’t have the problem but they’re issuing a performance hindering fix for the non-problem?

You seem confused padawan, MS imposed a OS patch that is a blanket patch without repercussions to effects on performance. AMD/INTEL are responsible for ucode fixes that mitigate that effect.
 
There are 2 patches that both needs to be applied. One OS, one microcode. MS have resumed patching on AMD systems after fixing the bricked Athlons due to poor documentation from AMD.
proof? For poor documentation.
 
proof? For poor documentation.
This page used to say that Microsoft was provided incorrect documentation by AMD about how some of their cpus and chipsets operate. Then they updated their page and removed that part of the official response. Still, you would think that they would've tested it. https://support.microsoft.com/en-us...urity-update-block-for-some-amd-based-devices

Here's a cached version https://webcache.googleusercontent....some-amd-based-devi+&cd=1&hl=en&ct=clnk&gl=us
Microsoft has reports of customers with some AMD devices getting into an unbootable state after installing recent Windows operating system security updates. After investigating, Microsoft has determined that some AMD chipsets do not conform to the documentation previously provided to Microsoft to develop the Windows operating system mitigations to protect against the chipset vulnerabilities known as Spectre and Meltdown. To prevent AMD customers from getting into an unbootable state, Microsoft will temporarily pause sending the following Windows operating system updates to devices with impacted AMD processors at this time:

January 3, 2018—KB4056897 (Security-only update)
January 9, 2018—KB4056894 (Monthly Rollup)
January 3, 2018—KB4056888 (OS Build 10586.1356)
January 3, 2018—KB4056892 (OS Build 16299.192)
January 3, 2018—KB4056891 (OS Build 15063.850)
January 3, 2018—KB4056890 (OS Build 14393.2007)
January 3, 2018—KB4056898 (Security-only update)
January 3, 2018—KB4056893 (OS Build 10240.17735)
January 9, 2018—KB4056895 (Monthly Rollup)
 
Last edited:
Guys, don't engage with Shintai when it comes to AMD, he has an almost pathological hatred of the company and cannot accept that they do anything right.

I'd love to know why this is.
 
The media just doesnt seem to understand... Er Pardon Kyle, the MAIN STREAM, not computer literate media, is clueless about Intel v AMD and dont get they are different or that a company other then Intel makes CPUs for home computers.

It stems more or less from the time AMD used to make Intel cpu and people calling x86 processors clones it goes way back. Many do not realize that AMD is the one with the 64 bit lead where Intel more or less "copied" AMD and because the most coverage goes to Intel what they are saying is gospel for the press there are only a few websites (compared to the masses that tend to be dead wrong) that really know what they are talking about regarding this whole subject.
So they are supplying fixed microcode, yet claims not affected. Good PR joke AMD :D

Every single OOO CPU is hit, no exception. And more to come in the future.

Did your new years resolution start with "must make the most amount of baseless claims on the www"?

Because you are striking out pretty much on every security topic I seen you post on the PSP stuff you posted in both Intel and AMD forums and now this, where do you get all of your "knowledge" from if so I would like valid links from atleast people who would know a lot more on the subject ..
 
Susceptible to spectre, just like every other modern cpu including arm, spectre is waaaaaaaaaay harder to use and is "slower", still yeah they are patching it.

Meltdown is the biggie in every way, threat wise and performance wise, this is a problem for Intel and some models of ARM processors.
Thanks for clearing that up.
 
what he meant was that windows ignores the cpu code(which is part of the mandatory statistics sent back to microsoft so there's no excuse for that) and downloads and installs the patch no matter what processor you have thus the issue amd athlon 64's ran into.. either way the problem is microsofts half ass lazy coding they've always been known for.

If you look at the scope of total eco systems they are responsible for, their patch process is actually pretty damn good. No other vender does better with maybe the exception of Apple because Apple has a very limited CLOSED eco-system of products.
 
I doubt you see a CPU free of this the next decade. The current only solution is to use slower in order designs that rely more on compilers. And the only known performance CPU in this area is Itanium.

I have a very hard time believing this.

Check out AMD Ryzen's Wiki Page .... that's a from scratch CPU design that was started in 2012. But you would have us believe Intel cannot fix this? That it would take a decade?

riiiiiiiiiiiiiiight .............
 
I doubt you see a CPU free of this the next decade. The current only solution is to use slower in order designs that rely more on compilers. And the only known performance CPU in this area is Itanium.

All they have to do is add a bounds check to the speculative address. Now if it's a physical fault of the L1 cache due to something like ROWHAMMER that corrupts jump addresses, then the L1 cache will have to be redesigned.
 
Another ignorant person. Please show me where AMD said that their CPU's are 100% not affected. Do you know what near zero means? It does not mean 100%, does it? Seriously...

They still hold to the point that it is near zero, so how has this changed?

You must be new here... Meet Shintel.
 
Back
Top