dbcve.org
Type ConfusionWeakness · CWE-843

CVE-2023-31323

HIGH · 8.4 CVSS v4.0 Published 2026-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Type confusion in the AMD Secure Processor (ASP) could allow an attacker to pass a malformed argument to the External Global Memory Interconnect Trusted Agent (XGMI TA) leading to a memory safety violation potentially resulting in loss of confidentiality, integrity, or availability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Type confusion vulnerability in AMD Secure Processor (ASP) allows malformed arguments to be passed to the External Global Memory Interconnect Trusted Agent (XGMI TA), causing a memory safety violation with potential for confidentiality, integrity, or availability loss.

MitigationApply AMD firmware updates for the Secure Processor as released through official AMD channels; verify the patch addresses the type confusion in XGMI TA argument handling.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm AMD Secure Processor presence
    Check system hardware for AMD Secure Processor (ASP) / AMD Platform Security Processor (PSP) using 'dmidecode' or system BIOS information. On Linux, examine /sys/devices/system/cpu/microcode or use 'lscpu' to verify AMD CPU with PSP capability.
    Affected if System lacks an AMD Secure Processor (not AMD hardware) - this CVE only applies to AMD systems with ASP.
  2. Retrieve AMD Secure Processor firmware version
    On Linux, check /sys/devices/platform/amd/pep/vbios_version or use AMD's PSP firmware version reporting tools if available. On Windows, use 'wmic' or AMD-specific diagnostics to query PSP firmware version.
    Affected if Unable to determine firmware version - the CVE is firmware-specific and requires version identification.
  3. Verify XGMI TA is enabled
    Determine if the External Global Memory Interconnect Trusted Agent (XGMI TA) is active on the system. This is typically a server/professional feature related to multi-socket GPU or CPU interconnects. Check system BIOS/UEFI settings or AMD utility outputs for XGMI TA module status.
    Affected if XGMI TA is disabled or not present - the vulnerability requires this specific trusted agent to be accessible for exploitation.
  4. Compare firmware version to affected range
    Compare your retrieved AMD Secure Processor firmware version against the known affected versions (if published by AMD). If no fixed version is published yet, note the current version for future comparison once patches are released.
    Affected if Firmware version falls within the affected range and XGMI TA is enabled - system is potentially vulnerable.

System is affected only if it has an AMD Secure Processor with vulnerable firmware AND has XGMI TA enabled; otherwise the attack surface does not exist.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply AMD firmware updates for the Secure Processor as released through official AMD channels; verify the patch addresses the type confusion in XGMI TA argument handling.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31323 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-31323 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data