dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-48516

MEDIUM · 6.9 CVSS v4.0 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
Insecure default configuration state of DDR5 memory module by AGESA Bootloader Firmware could allow an attacker with local user privilege to abuse the unprotected PMIC interface to create a permanent denial of service condition or affect the integrity of the memory module.

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

AGESA Bootloader Firmware for DDR5 memory modules has an insecure default configuration that leaves the PMIC (Power Management Integrated Circuit) interface unprotected. A local user with privilege access can exploit this unprotected interface to either permanently brick the memory module (denial of service) or modify memory module data integrity.

MitigationApply vendor-supplied BIOS/AGESA firmware updates from AMD and/or motherboard manufacturers that address the insecure default PMIC configuration in DDR5 memory initialization.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/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 processor and AGESA firmware in use
    Run 'dmidecode -t processor' or check BIOS/UEFI firmware information to identify the AMD processor and locate the AGESA version string (typically displayed as 'AGESA xxx' in BIOS info)
    Affected if System uses an AMD processor with AGESA Bootloader Firmware for DDR5 memory initialization
  2. Verify DDR5 memory modules are installed
    Run 'dmidecode -t memory' or check system information to confirm DDR5-type memory modules are present
    Affected if DDR5 memory modules are installed in the system
  3. Check AGESA firmware version
    Locate the AGESA version in BIOS/UEFI settings under 'BIOS Information' or 'Mainboard Information', or use tools like CPU-Z to read the AGESA version
    Affected if Installed AGESA version falls within the affected version range (compare your version to the affected ranges if known)
  4. Inspect PMIC configuration in BIOS/UEFI
    Enter BIOS/UEFI setup and navigate to memory or power management settings to locate PMIC (Power Management IC) configuration options; check if the interface remains in default unsecured settings
    Affected if PMIC interface configuration shows default/unprotected state or lacks explicit security controls enabled

A user is affected if they run an AMD system with DDR5 memory using an AGESA Bootloader Firmware version with the PMIC interface left in its default unprotected configuration.

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 vendor-supplied BIOS/AGESA firmware updates from AMD and/or motherboard manufacturers that address the insecure default PMIC configuration in DDR5 memory initialization.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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