Exclusive: Here’s The Deal About AMD’s Stolen GPU IP
So AMD's GPU IP theft has been making headlines and while no one was sure what got stolen, we were able to talk to multiple individuals (who wish to remain anonymous for obvious reasons) that not only viewed the files while they were on GitHub, but have vast experience with Verilog (the software the files are written in) and microarchitecture design. What they told us is in-line with the official statement made by AMD and something AMD investors and fans would be glad to hear.
No, the stolen IP doesn't represent a "source code" to building and designing an AMD RDNA GPU, not even close
AMD has already given its official statement on the issue and while the company made it clear that it will be pursuing the theft under the full extent of the law and it consists of "just a subset", it doesn't provide any details that readers would be looking to hear. This article is a short write up to remedy that. For the purposes of this article, I am simply going to note down the main takeaways from my chat.
Here is what the AMD GPU IP leak actually is:
- Partial Verilog files that are typically used in the construction of processors.
- The Verilog files in question represent a single and isolated function(s) on the GPU - NOT the whole/actual GPU blueprint. This I believe is the most important takeaway and context for the IP theft. This particular function(s) is not very exciting and not part of AMD's core IP.
- Based on the leaker's screenshots, the files they have not yet leaked are more of the same and also nowhere close to being a complete "source code". In other words, the total stolen IP represents a very small fraction of the "source code" needed to build and design a GPU.
- These Verilog files are built on a proprietary schematic that is only compatible with AMD's internal design language (in other words, these are going to be close to useless to a third party).
Here is what the AMD GPU IP leak is not:
- It cannot be used to design or build any of the mentioned products - not even close.
- It cannot be used to reverse engineer product performance.
- It cannot be used to easily reverse engineer any features/product specifications. This comment is based on the files leaked so far. The source estimates that it may be possible for the full list of files to be used to arrive at a couple of very high-level specifications but this should not be an issue because most of this information is already public.
- It does not contain any data that can be used to easily/immediately bypass any security features on AMD RDNA GPUs. Caveat: there is a very slim possibility that it may be used to discover a vulnerability in the functions stolen in this theft.
- It does not contain any "crown jewel" IP. In fact, I am told that this would not even constitute a "significant" theft to a company like AMD in terms of the severity of the information compromised (any theft is still very significant by virtue of the act of course).
Our source(s) also stated that it was very unlikely that the hacker would just come across an unprotected/unencrypted PC as this type of IP is usually protected behind a chain of trust and other SOPs. While the stolen IP itself is just a subset of test IP (remember, these are just isolated functions, not a whole RDNA GPU blueprint) it is likely that the criminal investigation will turn up something more notorious than just happening across an unencrypted PC. That said, I am sure this security lapse will result in the company ramping up security procedures and SOPs.
Oh and for those interested, here is AMD's official statement on the theft:
At AMD, data security and the protection of our intellectual property are a priority. In December 2019, we were contacted by someone who claimed to have test files related to a subset of our current and future graphics products, some of which were recently posted online, but have since been taken down.
While we are aware the perpetrator has additional files that have not been made public, we believe the stolen graphics IP is not core to the competitiveness or security of our graphics products. We are not aware of the perpetrator possessing any other AMD IP.
We are working closely with law enforcement officials and other experts as a part of an ongoing criminal investigation. - AMD