dbcve.org
RocmApplication · Amd

CVE-2023-31324

HIGH · 7.8 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 6.2.0 / 24.6.1 or later.
See remediation →
80/100
Remediation priority · High
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
A Time-of-check time-of-use (TOCTOU) race condition in the AMD Secure Processor (ASP) could allow an attacker to modify External Global Memory Interconnect Trusted Agent (XGMI TA) commands as they are processed 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

A TOCTOU race condition in the AMD Secure Processor allows attackers to modify XGMI Trusted Agent commands as they are being processed, potentially compromising confidentiality, integrity, or availability of the affected system.

MitigationApply AMD firmware updates for the Secure Processor when available; until then, restrict physical access and monitor for suspicious activity targeting the ASP.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RocmApplication
Affected:< 6.2.0
Radeon SoftwareApplication
Affected:< 25.q2< 24.6.1
Radeon Pro Vii FirmwareOperating system
Affected:all versions
Radeon Vii FirmwareOperating system
Affected:all versions

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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

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. Check ROCm version
    Run 'rocminfo' or check /opt/rocm/bin/ for rocminfo; also check package manager for installed ROCm packages with 'dpkg -l | grep rocm' or 'rpm -qa | grep rocm'
    Affected if ROCm version is installed and less than 6.2.0
  2. Check AMD Radeon Software version
    Check installed AMD driver package version via 'dxdiag' on Windows, or look for /usr/share/X11/xorg.conf.d/ for AMD driver files; check System Preferences > About This Mac on macOS for AMD GPU drivers
    Affected if AMD Radeon Software version is present and less than 24.6.1 or less than 25.q2 (for quarterly releases)
  3. Identify Radeon Pro VII GPU and firmware
    Run 'lspci | grep -i vga' or 'lspci | grep -i radeon' to find Radeon Pro VII; then check firmware version via 'cat /sys/class/drm/card0/device/firmware_node' or use 'amdvlk' / 'rocm-smi' if available
    Affected if Radeon Pro VII GPU is present (firmware is vulnerable on all versions)
  4. Identify Radeon VII GPU and firmware
    Run 'lspci | grep -i radeon' to detect Radeon VII; check firmware via 'dmesg | grep -i radeon' at boot or use GPU info tools
    Affected if Radeon VII GPU is present (firmware is vulnerable on all versions)

You are affected if any ROCm version below 6.2.0, Radeon Software below 24.6.1/25.q2, or any Radeon Pro VII/Radeon VII GPU with firmware is present in your environment.

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.

dbcve · scoped
Upgrade available Upgrade to 6.2.0 / 24.6.1 / 25.q2 or later
Fixed in 6.2.024.6.125.q2
Interim mitigation

Apply AMD firmware updates for the Secure Processor when available; until then, restrict physical access and monitor for suspicious activity targeting the ASP.

Recommended fix Moderate confidence

Rocm: 6.2.0+ | Radeon Software Windows: 25.q2+ | Radeon Software Linux: 24.6.1+ | Firmware: Contact AMD for update

  1. 1. Identify the specific AMD product(s) in your environment from the affected list: Rocm, Radeon Software, Radeon Pro Vii Firmware, or Radeon Vii Firmware
  2. 2. For Rocm installations: Upgrade to version 6.2.0 or later by following AMD's ROCm installation documentation for your operating system
  3. 3. For Radeon Software (Windows): Upgrade to version 25.q2 or later via AMD Radeon Software auto-update or by downloading from amd.com/support
  4. 4. For Radeon Software (Linux): Upgrade to version 24.6.1 or later through your distribution's package manager or AMD's driver download page
  5. 5. For Radeon Pro Vii and Radeon Vii Firmware: Contact AMD support or check amd.com for firmware updates addressing this vulnerability; firmware updates may require following AMD's specific firmware flashing procedure
Caveat Review AMD release notes for ROCm 6.2.0 and Radeon Software 24.6.1/25.q2 for any driver or software compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rocm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31324 — 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-31324 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