VulnerabilityPublished 10 Feb 2026

CVE-2024-36311: AMD Ryzen™ 7045 Series Mobile Processors with Radeon™ Graphics · Time-of-check Time-of-use (TOCTOU) Race Condition

Affects AMD Ryzen™ 7045 Series Mobile Processors with Radeon™ GraphicsSource CVE Database V5

Not known to be exploited · CVSS 4.6 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

4.6Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
AMDAMD Ryzen™ 7045 Series Mobile Processors with Radeon™ Graphics	Affected–	Fixed in–
AMDAMD Ryzen™ 7000 Series Desktop Processors	Affected–	Fixed in–
AMDAMD Ryzen™ 9000HX Series Mobile Processors	Affected–	Fixed in–
AMDAMD Ryzen™ 8000 Series Desktop Processors	Affected–	Fixed in–
AMDAMD Ryzen™ 9000 Series Desktop Processors	Affected–	Fixed in–
AMDAMD Ryzen™ Embedded 7000 Series Processors	Affected–	Fixed in–

AI-suggested

Monitor AMD’s official channels for firmware updates addressing CVE-2024-36311 and apply them promptly once available.
Implement strict access controls to limit privileged local access to trusted administrators only, reducing the risk of exploitation.
Employ endpoint security solutions capable of detecting anomalous behavior indicative of attempts to exploit race conditions or memory corruption.
Conduct regular security audits and privilege reviews on systems using affected processors to ensure minimal privilege principles are enforced.
Educate IT staff about the risks associated with TOCTOU vulnerabilities and the importance of timely patching and access management.
For high-security environments, consider additional hardware-based protections or isolation techniques to limit SMM exposure.
Maintain comprehensive logging and monitoring to detect potential exploitation attempts or suspicious activity related to SMM communications.
Coordinate with hardware vendors and security teams to integrate vulnerability management into the broader cybersecurity strategy.

Description

A Time-of-check time-of-use (TOCTOU) race condition in the SMM communications buffer could allow a privileged attacker to bypass input validation and perform an out of bounds read or write, potentially resulting in loss of confidentiality, integrity, or availability.

Impact

For European organizations, this vulnerability poses a risk primarily in environments where AMD Ryzen 7045 Series Mobile Processors are deployed in laptops or mobile workstations, especially in sectors handling sensitive or regulated data. Successful exploitation could lead to unauthorized disclosure of confidential information, unauthorized modification of critical system data, or denial of service through system instability. This is particularly relevant for enterprises with remote or hybrid workforces using mobile devices that may be physically accessible to attackers or exposed to insider threats. The requirement for privileged local access limits remote exploitation risk but does not eliminate insider threat or post-compromise lateral movement scenarios. The potential impact on confidentiality, integrity, and availability could disrupt business operations, lead to data breaches, or compromise compliance with data protection regulations such as GDPR. Given the medium severity, the threat is significant but not urgent, allowing organizations time to plan and deploy mitigations. However, failure to address this vulnerability could increase risk exposure in high-security environments or industries with stringent cybersecurity requirements.

CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
Implementation
The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.
Implementation
When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement.
Architecture and Design
Limit the interleaving of operations on files from multiple processes.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.3 (opens in a new tab)
V11.1.6 (opens in a new tab)
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Race Conditions via Symbolic Links (opens in a new tab)
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

amd.com/en/resources/product-security/bulletin/AMD-SB-4013.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Feb 2026, 20:17 UTC

WeaknessesCWE-367

Technical details

References

Community reviews

Related threats