CVE-2021-26380: A compromised Trusted OS (TOS) driver could issue a malformed call that could potentially allow memory acc...
A compromised Trusted OS (TOS) driver could issue a malformed call that could potentially allow memory access outside the intended range resulting in loss of integrity.
Security readout for executives and security teams
Plain-English summary
CVE-2021-26380 is a low-severity AMD Trusted OS issue. A compromised Trusted OS driver could make a malformed call and access memory outside its intended range, affecting integrity. It is not described as remotely exploitable and has demanding prerequisites.
Executive priority
Handle through normal vulnerability management unless the affected systems protect high-value workloads. The low CVSS score and high prerequisites reduce urgency, but firmware/software coverage can be operationally slow.
Technical view
The issue is mapped to CWE-190 and involves malformed calls from a compromised TOS driver causing out-of-range memory access. CVSS 4.0 is 1.8: local attack vector, high complexity, high privileges, no user interaction, and low confidentiality and integrity impact.
Likely exposure
Exposure is limited to listed AMD Ryzen, Athlon, Embedded, Radeon RX, and Radeon PRO products running affected firmware or AMD software versions. Asset inventory and OEM firmware/software state determine relevance.
Exploitation context
The source bundle does not identify active exploitation, and KEV is false. The described prerequisite is already serious: a compromised Trusted OS driver with local, high-privilege conditions, making this primarily a post-compromise integrity concern.
Researcher notes
Evidence is incomplete for exploit availability and fixed-version details in the provided bundle. Validation should focus on product/version matching and AMD bulletin interpretation, not proof-of-concept testing.
Mitigation direction
Review AMD-SB-4017 and AMD-SB-6027 for product-specific guidance.
Check OEM BIOS, firmware, and AMD software update channels for applicable fixes.
Prioritize systems where listed AMD products run sensitive workloads.
Track remediation separately for desktop, mobile, embedded, and graphics products.
Validation and detection
Inventory systems for the affected AMD product families listed in the CVE bundle.
Record current BIOS, firmware, AGESA, and AMD software versions.
Compare installed versions against AMD and OEM security guidance.
Confirm whether systems rely on Trusted OS or secure execution features.
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-190: 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-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.