dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-36326

HIGH · 8.4 CVSS v3.1 Published 2025-09-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/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
Missing authorization in AMD RomArmor could allow an attacker to bypass ROMArmor protections during system resume from a standby state, potentially resulting in a loss of confidentiality and integrity.

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 · moderate confidence

AMD RomArmor is a firmware-based security feature that protects the read-only memory (ROM) of AMD processors from modification. This vulnerability involves a missing authorization check that allows an attacker to bypass RomArmor protections specifically during system resume from a standby (S3) state. By exploiting this flaw, an attacker could potentially read or modify protected firmware/ROM contents, leading to loss of confidentiality and integrity of the system's boot chain.

MitigationApply AMD firmware/BIOS updates as they become available. Until patches are released, ensure physical security of affected systems and monitor for unauthorized physical access attempts during standby/resume cycles.

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

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

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. Verify AMD processor with RomArmor support
    Check system information to confirm an AMD processor is in use. On Windows, run 'wmic cpu get name,manufacturer' or check System Information. On Linux, run 'cat /proc/cpuinfo' and look for AMD processor info. RomArmor is an AMD-specific feature.
    Affected if System uses a non-AMD processor - RomArmor is an AMD-specific firmware protection feature and this CVE does not apply.
  2. Confirm RomArmor is enabled in BIOS/UEFI
    Enter system BIOS/UEFI settings during boot (typically press Del, F2, or F10). Navigate to security or firmware protection settings. Look for RomArmor, AMD Platform Security Processor, or similar firmware protection options.
    Affected if RomArmor is disabled in BIOS/UEFI settings - the bypass vulnerability does not apply as the protection is not active.
  3. Identify current BIOS/UEFI firmware version
    On Windows, run 'wmic bios get smbiosbiosversion' or check the BIOS version shown in System Information (Win + R, type 'msinfo32'). On Linux, check 'cat /sys/class/dmi/id/bios_version' or use 'dmidecode -s bios-version'. Compare against any AMD advisory releases.
    Affected if Unable to determine BIOS version or version is unknown - proper detection requires comparing installed BIOS version against AMD's fixed versions once released.
  4. Check S3 standby/resume configuration
    On Windows, open Power Options (control panel) and verify if S3 sleep states are available or enabled. On Linux, check 'cat /sys/power/state' to see available sleep states. The vulnerability is specifically triggered during S3 resume.
    Affected if System does not support or use S3 standby/resume - the attack vector requires the S3 resume path to be exploitable.
  5. Review firmware update availability
    Check AMD's official support website or your system manufacturer's support page for any available BIOS/firmware updates addressing CVE-2024-36326. Note that at the time of this CVE, patches may not yet be released.
    Affected if A BIOS update specifically addressing this CVE is available and installed - patches supersede the vulnerable code path.

A system is affected if it uses an AMD processor with RomArmor enabled in BIOS/UEFI, supports S3 standby/resume, and has not yet received the AMD firmware update that addresses this missing authorization check during S3 resume.

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/BIOS updates as they become available. Until patches are released, ensure physical security of affected systems and monitor for unauthorized physical access attempts during standby/resume cycles.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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