AMD Warns of Transient Scheduler Attacks Affecting Wide Range of Chipsets


Advanced Micro Devices has disclosed a series of critical security vulnerabilities affecting multiple generations of its processor architectures, stemming from transient scheduler attacks that exploit speculative execution mechanisms.

The vulnerabilities, identified through four distinct Common Vulnerabilities and Exposures (CVE) entries, pose significant risks to data confidentiality across enterprise and consumer computing environments.

The security flaws emerged following investigations into a Microsoft research report titled “Enter, Exit, Page Fault, Leak: Testing Isolation Boundaries for Microarchitectural Leaks.”

Google News

The vulnerabilities leverage timing-based side channels in AMD’s microarchitectural implementations, allowing attackers to infer sensitive information from system memory and processor states through carefully crafted speculative execution sequences.

AMD analysts identified these transient execution vulnerabilities as capable of bypassing traditional security boundaries, potentially exposing privileged information across different execution contexts.

The attacks target fundamental processor operations including store-to-load forwarding, L1 data cache interactions, and control register access mechanisms, creating opportunities for unauthorized data extraction.

The impact spans across AMD’s extensive processor portfolio, including third and fourth-generation EPYC server processors, Ryzen desktop and mobile processors from the 5000 through 8000 series, Threadripper workstation processors, and various embedded computing platforms.

The vulnerabilities particularly affect processors utilizing the Zen 3 and Zen 4 architectures, with some earlier generation processors remaining unaffected.

Speculative Execution Exploitation Mechanism

The attack methodology centers on manipulating the processor’s speculative execution engine to create measurable timing differences that leak information about memory contents and system state.

CVE-2024-36350 and CVE-2024-36357, both carrying CVSS scores of 5.6, represent the most severe vulnerabilities by enabling attackers to infer data from previous store operations and L1D cache contents respectively.

CVE IDCVSS ScoreCVSS VectorVulnerability TypeDescriptionAttack RequirementsMitigation StatusTimeline
CVE-2024-363505.6 (Medium)AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:NTransient Execution – Store Data InferenceAllows attackers to infer data from previous stores, potentially resulting in leakage of privileged informationLocal access, High complexity, Low privilegesFirmware + OS Updates RequiredDec 2024 – Jan 2025
CVE-2024-363575.6 (Medium)AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:NTransient Execution – L1D Cache Data InferenceEnables attackers to infer data in the L1D cache, potentially leaking sensitive information across privileged boundariesLocal access, High complexity, Low privilegesFirmware + OS Updates RequiredDec 2024 – Jan 2025
CVE-2024-363483.8 (Low)AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:NTransient Execution – Control Register InferenceAllows user processes to infer control registers speculatively even when UMIP feature is enabledLocal access, Low complexity, Low privilegesNo fix planned for most processorsNo fix planned
CVE-2024-363493.8 (Low)AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:NTransient Execution – TSC_AUX InferencePermits user processes to infer TSC_AUX even when such reads are disabledLocal access, Low complexity, Low privilegesNo fix planned for most processorsNo fix planned

These attacks exploit the processor’s attempt to optimize performance through speculative execution, turning this efficiency mechanism into a security liability.

The vulnerabilities require local access and specific microarchitectural conditions to trigger successfully, limiting their practical exploitation to scenarios where attackers already possess some level of system access.

However, the potential for cross-privilege boundary information leakage makes these vulnerabilities particularly concerning for multi-tenant environments and virtualized infrastructures.

AMD’s mitigation strategy involves coordinated firmware and operating system updates, with Platform Initialization firmware releases scheduled throughout 2024 and 2025.

Organizations must implement both firmware updates from original equipment manufacturers and corresponding operating system patches to achieve complete protection against these sophisticated microarchitectural attacks.

Investigate live malware behavior, trace every step of an attack, and make faster, smarter security decisions -> Try ANY.RUN now



Source link