{"id":4822,"date":"2024-08-12T15:14:47","date_gmt":"2024-08-12T20:14:47","guid":{"rendered":"https:\/\/www.darkreading.com\/remote-workforce\/amd-issues-updates-for-silicon-level-sinkclose-flaw"},"modified":"2024-08-12T15:14:47","modified_gmt":"2024-08-12T20:14:47","slug":"amd-issues-updates-for-silicon-level-sinkclose-processor-flaw","status":"publish","type":"post","link":"https:\/\/ddi.mohflo.net\/index.php\/2024\/08\/12\/amd-issues-updates-for-silicon-level-sinkclose-processor-flaw\/","title":{"rendered":"AMD Issues Updates for Silicon-Level ‘SinkClose’ Processor Flaw"},"content":{"rendered":"
<\/a><\/div>\n
<\/div>\n

AMD has issued firmware updates to address a nearly two-decades-old silicon-level vulnerability it its EPYC data center processors and its line of Ryzen processors for PCs and embedded systems.<\/span><\/p>\n

The flaw affects a component in the processor for protecting System Management Mode (SMM), an execution mode so protected in the processor that it is even more privileged than kernel-level mode. Researchers from IOActive who discovered the privilege escalation vulnerability described it as an “unpatchable” issue that, if exploited, would allow an attacker to implant malware on a system that would be almost impervious to removal attempts.<\/span><\/p>\n

Hundreds of millions of devices worldwide currently have AMD chips that contain the vulnerability.<\/span><\/p>\n

The SinkClose Flaw<\/h2>\n

The “SinkClose” vulnerability, as IOActive researchers have dubbed it, is somewhat similar to “<\/span>Memory Sinkhole<\/a><\/span>,” an SMM-bypass vulnerability in Intel Sandy Bridge and prior processors that security researcher Christopher Domas disclosed at a Black Hat presentation in 2015. Domas has also uncovered <\/span>other hardware level vulnerabilities<\/a><\/span> in Intel chips.<\/span><\/p>\n

“The vulnerability is nearly impossible to fix in computers that aren’t configured correctly \u2014 which is the case for most systems,” IOActive said in a statement. “In properly configured systems, the vulnerability could lead to malware infections \u2014 known as bootkits \u2014 that are nearly impossible to detect.”<\/span><\/p>\n

AMD itself has described the vulnerability as an issue that gives attackers who already have ring0 \u2014 or kernel level \u2014 access to an affected system a way to potentially modify the SMM even if SMM Lock, a feature for preventing unauthorized SMM modifications, is turned on. “Improper validation in a model specific register (MSR) could allow a malicious program with ring0 access to modify SMM configuration while SMM Lock is enabled, potentially leading to arbitrary code execution,” <\/span>the chip vendor said<\/a><\/span>.<\/span><\/p>\n

SMM is a mode on AMD chips for <\/span>low-level system management functions<\/a><\/span>. It only executes code from a segregated block of memory called system management random access memory, or SMRAM. AMD chips implement a memory controller called TSeg to protect access to SMRAM.<\/span><\/p>\n

SMM Bypass Attack<\/h2>\n

However, IOActive researchers Enrique Nissim and Krzysztof Okupski found a way to overcome these protections and get SMM to essentially execute code of their choice from outside the SMRAM. They did this by leveraging a feature called TClose that AMD incorporated into its chips for backward compatibility with a legacy memory management feature. Dumas’ SinkHole flaw involved a similar legacy feature in Intel chips.<\/span><\/p>\n

Nissim and Okupski determined an attacker could use the SinkClose flaw to drop malware deep enough \u2014 and persistent enough \u2014 inside a system to make it invisible to the operating system, the hypervisor, and to all endpoint detection mechanisms. In a talk at the DEF CON hacker conference on Aug. 10, the researchers described the vulnerability as something a remote attacker would be able to exploit. However, an adversary would need an in-depth understanding of AMD chip architecture \u2014 something that only a nation-state-level would likely possess \u2014 to be able to exploit it.<\/span><\/p>\n

AMD itself has contended by way of background context that an attacker with the level of access required to exploit the SinkClose vulnerability would already have the ability to read, modify, erase, and snoop on everything on the computer. In addition, someone with operating system kernel-level access can also disable security mechanisms and prevent a computer from booting.<\/span><\/p>\n

“This is akin to having the knowledge to break into a safe deposit box at the bank,” AMD noted in an email to Dark Reading. “In the real world, to get to the box, a burglar must first get past the alarms, the guards, the vault door and its own locks, clearly not an easy task.”<\/span><\/p>\n

An attacker with the skills and knowledge to execute an SMM bypass attack could install malware of the sort IOActive has warned about. But it wouldn’t be the first time attackers have deployed such malware, AMD said by way of background, pointing to the <\/span>Lojax firmware-level rootkit<\/a><\/span> from 2018. “While this malware may be stealthy, it is not invisible or impossible to remediate.”<\/span><\/p>\n

“AMD has released mitigation options for its AMD EPYC datacenter products and AMD Ryzen PC products,” the chipmaker said. “A full list of impacted products and mitigation options is available in our <\/span>product security bulletin<\/a><\/span>.”<\/span><\/p>\n

Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

AMD has issued firmware updates to address a nearly two-decades-old<\/p>\n","protected":false},"author":12,"featured_media":4823,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[809],"class_list":["post-4822","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-dark-reading"],"featured_image_urls":{"full":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/08\/amd-issues-updates-for-silicon-level-sinkclose-processor-flaw.jpg?fit=1920%2C1080&ssl=1",1920,1080,false],"thumbnail":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/08\/amd-issues-updates-for-silicon-level-sinkclose-processor-flaw.jpg?resize=150%2C150&ssl=1",150,150,true],"medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/08\/amd-issues-updates-for-silicon-level-sinkclose-processor-flaw.jpg?fit=300%2C169&ssl=1",300,169,true],"medium_large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/08\/amd-issues-updates-for-silicon-level-sinkclose-processor-flaw.jpg?fit=640%2C360&ssl=1",640,360,true],"large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/08\/amd-issues-updates-for-silicon-level-sinkclose-processor-flaw.jpg?fit=640%2C360&ssl=1",640,360,true],"1536x1536":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/08\/amd-issues-updates-for-silicon-level-sinkclose-processor-flaw.jpg?fit=1536%2C864&ssl=1",1536,864,true],"2048x2048":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/08\/amd-issues-updates-for-silicon-level-sinkclose-processor-flaw.jpg?fit=1920%2C1080&ssl=1",1920,1080,true],"chromenews-featured":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/08\/amd-issues-updates-for-silicon-level-sinkclose-processor-flaw.jpg?fit=1024%2C576&ssl=1",1024,576,true],"chromenews-large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/08\/amd-issues-updates-for-silicon-level-sinkclose-processor-flaw.jpg?resize=825%2C575&ssl=1",825,575,true],"chromenews-medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/08\/amd-issues-updates-for-silicon-level-sinkclose-processor-flaw.jpg?resize=590%2C410&ssl=1",590,410,true]},"author_info":{"display_name":"Dark Reading","author_link":"https:\/\/ddi.mohflo.net\/index.php\/author\/darkreading\/"},"category_info":"Uncategorized<\/a>","tag_info":"Uncategorized","comment_count":"0","jetpack_featured_media_url":"https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/08\/amd-issues-updates-for-silicon-level-sinkclose-processor-flaw.jpg?fit=1920%2C1080&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/4822","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/comments?post=4822"}],"version-history":[{"count":0,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/4822\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media\/4823"}],"wp:attachment":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media?parent=4822"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/categories?post=4822"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/tags?post=4822"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}