CVE-2022-23826: A TOCTOU (Time-Of-Check to Time-Of-Use) in the graphics interface may allow an attacker to load registers r...
A TOCTOU (Time-Of-Check to Time-Of-Use) in the graphics interface may allow an attacker to load registers repeatedly creating a race condition potentially leading to a loss of integrity.
Security readout for executives and security teams
Plain-English summary
CVE-2022-23826 is a low-severity AMD graphics-interface race-condition issue. A highly privileged local attacker could repeatedly load registers in a way that may affect integrity. The public record does not indicate remote attack, unauthenticated attack, or confirmed active exploitation.
Executive priority
Handle through normal patch governance unless the affected GPUs are in shared, sensitive, or multi-tenant environments. The business urgency is low, but unresolved firmware and driver exposure should be tracked to closure.
Technical view
The issue is classified as CWE-367, a time-of-check to time-of-use flaw in AMD graphics handling. CVSS 4.0 is 1.8 with local access, high attack complexity, and high privileges required. Impact is limited to low confidentiality, integrity, and availability effects on vulnerable AMD processor, Radeon, Instinct, and PRO product lines.
Likely exposure
Exposure is most relevant on systems using the listed AMD Radeon, Radeon PRO, Instinct, Ryzen Embedded, Ryzen Mobile, or Athlon products. Risk is reduced by the required local access, high privileges, and high complexity.
Exploitation context
The provided sources mark this as not in CISA KEV and do not cite exploitation in the wild. The attack conditions require local access and high privileges, so this is mainly a defense-in-depth and fleet hygiene issue.
Researcher notes
Evidence is limited to the CVE record and AMD bulletins. The record describes integrity loss from a TOCTOU race in the graphics interface but does not provide exploit mechanics, public exploit status, or a universal remediation path.
Mitigation direction
Review AMD-SB-4017 and AMD-SB-6027 for product-specific guidance.
Update BIOS, firmware, graphics drivers, or ROCm only through AMD or OEM channels.
For MI25 and PRO V520, contact AMD Customer Engineering as referenced.
Prioritize shared GPU, workstation, and high-privilege multi-user environments.
Validation and detection
Inventory systems with listed AMD processor, Radeon, Radeon PRO, and Instinct products.
Compare installed BIOS, driver, and ROCm versions against AMD bulletins.
Confirm whether untrusted local administrators can run GPU workloads.
Document exceptions where AMD guidance requires vendor or customer-engineering follow-up.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-367: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-367 · source CWE mapping
Time-of-check Time-of-use (TOCTOU) Race Condition
Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.