AMD Issues Warning: New Transient Scheduler Attacks Affect Multiple CPUs

Published:

New Vulnerabilities Discovered in AMD Chipsets: Transient Scheduler Attacks

Overview of the Vulnerabilities

AMD, a leading semiconductor manufacturer, has recently issued warnings about a series of vulnerabilities impacting various chipsets. These vulnerabilities, grouped under the term Transient Scheduler Attacks (TSA), present significant risks related to information disclosure. The root of these flaws lies in a speculative side channel embedded within AMD CPUs, which exploit specific timing conditions during instruction execution.

Mechanism Behind Transient Scheduler Attacks

The vulnerabilities arise from how instructions are executed and their timing. According to AMD’s advisory, there is a risk that an attacker could leverage timing data to extract sensitive information from different contexts, potentially leading to data leakage. The vulnerabilities came to light as part of research conducted by Microsoft and ETH Zurich. This study aimed at testing modern CPUs against various speculative execution attacks, such as those seen in previous notorious exploits like Meltdown and Foreshadow. The focus was on examining isolation between security domains, including virtual machines and kernel processes.

Details of the Identified Vulnerabilities

AMD has assigned several Common Vulnerabilities and Exposures (CVE) identifiers to these issues. The relevant CVEs are as follows:

  • CVE-2024-36350 (CVSS score: 5.6): This vulnerability allows attackers to infer previously stored data, which can result in leaking privileged information.
  • CVE-2024-36357 (CVSS score: 5.6): Similar to the previous CVE, it pertains to the potential data leakage from the L1 Data cache across privilege boundaries.
  • CVE-2024-36348 (CVSS score: 3.8): This flaw could allow user processes to infer speculative control register data, even when safeguards like UMIP are in place.
  • CVE-2024-36349 (CVSS score: 3.8): This involves the capacity to infer TSC_AUX data speculative, despite restrictions, potentially leading to further information leakage.

Affected Products and Mitigation Measures

AMD has identified a wide range of processors affected by the TSA vulnerabilities. The following product lines are at risk:

  • 3rd and 4th Generation AMD EPYC Processors
  • AMD Instinct MI300A
  • AMD Ryzen 5000, 7000, and 8000 Series Desktop Processors
  • AMD Threadripper PRO 7000 WX-Series
  • AMD EPYC Embedded Series

To address these vulnerabilities, the company has issued microcode updates for the affected processors.

Understanding False Completion

One of the crucial aspects of these vulnerabilities is the phenomenon known as false completion. This occurs when CPU hardware anticipates that a memory load instruction will complete quickly, yet circumstances hinder that completion. As a result, dependent operations may be executed prematurely, based on the invalid data from the unsuccessful load. Unlike other speculative behaviors that lead to a pipeline flush, false completions do not clear the processor state, allowing invalid data to potentially influence subsequent operations.

Types of TSA Vulnerabilities

AMD has categorized the TSA vulnerabilities into two variants: TSA-L1 and TSA-SQ. The TSA-L1 vulnerability originates from errors in how the L1 cache handles microtags during data-cache lookups. Conversely, TSA-SQ vulnerabilities arise when load instructions erroneously pull data from the CPU’s store queue when it is not yet accessible. In both cases, attackers could exploit this to infer data executed within different contexts.

Exploitation Scenario

While the implications of these vulnerabilities are serious, exploiting them is not straightforward. An attacker would need to gain malicious access to a targeted machine and possess the capability to execute arbitrary code—making compensation for this a significant hurdle. Successful exploitation would typically require repeated engagement with the victim to recreate the conditions necessary for false completions. Such exploitation is most feasible in scenarios where there is already communication between the victim and attacker, like between an application and the operating system kernel.

Conclusion

AMD’s identification and disclosure of the Transient Scheduler Attacks are crucial steps in addressing vulnerabilities in modern CPU architectures. Their proactive measures, including microcode updates, will play an essential role in bolstering security for users while reinforcing AMD’s commitment to safeguarding sensitive data against emerging threats.

For ongoing updates and additional technical guidance, following AMD’s official communications is highly recommended.

CHAPTER X // CYBER AWARENESS CAMPAIGN
BEYOND THE BALLROOM
[C://ME] // CHAPTER X

REQUEST THE MEDIA KIT

Tell us where to send the Beyond the Ballroom media deck. Every field is required.

We will use these details to respond to your media-kit request. Privacy Policy

Cyber Warriors Conclave Chapter X — Beyond the Ballroom

Related articles

Recent articles

CrowdStrike identifies critical NGINX vulnerabilities (CVE-2026-123007 et al.) enabling remote code execution

On November 18, 2026, CrowdStrike disclosed a set of five critical vulnerabilities in NGINX, a widely used open-source web server, collectively termed NGINX2Root. These...

CTO of RansomwareHelp indicted for wire fraud in FBI sting operation

The chief technology officer and co-founder of ransomwarehelp.com, a Florida-based company that claimed to utilize “advanced cryptographic tools” to restore data locked by ransomware,...

AI supply chain breaches expose user data as researchers reveal prompt theft and security failures

Recent research has unveiled significant security vulnerabilities within the AI supply chain, revealing that at least three AI providers were compromised, leading to the...

Red Hat releases important sos security update for multiple RHEL versions

Red Hat has announced a significant security update for its sos package, affecting multiple versions of Red Hat Enterprise Linux (RHEL). This update addresses...