CVE-2025-54518
Raw vector
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/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:XSummary
CVE-2025-54518 is a high-severity SoC (CWE-1189) vulnerability in Amd (inferred from references). Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Services File Permissions Weakness (T1574.010); ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-209882
Vulnerability Data
Improper isolation of shared resources within the CPU operation cache on Zen 2-based products could allow an attacker to corrupt instructions executed at a different privilege level, potentially resulting in privilege escalation.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 4 OS baselines
V16.4.2V8.4.2V11.7.1V13.2.4
Mitigating Controls (NIST 800-53 r5) AI
Least privilege explicitly demands that only the minimum necessary accesses are granted, eliminating the broad permissions that define this weakness.
SC-4 explicitly prevents unauthorized information transfer via shared system resources, addressing the core SoC isolation failure.
SC-49 mandates hardware-enforced separation between security domains, directly countering improper SoC resource isolation.
AC-24 requires access decisions to be applied precisely and unambiguously to every request, structurally blocking insufficiently granular policies.
AC-3 requires enforcement of authorizations according to policy, directly compelling sufficiently granular rules so broad allowances cannot be introduced.
SC-32 requires partitioning the system into separate domains, structurally preventing shared-resource leakage on an SoC.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.IR-01's segmentation + zero-trust rules directly enforce minimum-necessary access at network boundaries, removing most instances of overly broad policy; CWE-1220 can still exist in application-layer or intra-segment controls that this single outcome does not address.
Contractual requirements on suppliers can mandate proper SoC resource isolation.
Hardware integrity/authenticity checks before acquisition can verify isolation features.
Supplier assessments can evaluate SoC isolation capabilities prior to purchase.
PR.PS-06's general SDLC practices can surface granularity issues during design/review (partial prevention) but do not specifically target access-control policy breadth, so they remove only part of CWE-1220's risk.
CWE-1220 permits unauthorized access to sensitive assets but neither prevents nor impairs the delivery of adverse-event information to authorized recipients.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure system architecture and engineering principles directly require hardware-level isolation of shared SoC resources.
Security testing can detect SoC isolation issues but does not prevent the weakness from existing in the design.
Directly requires information-access restriction at the level of individual assets and operations, addressing the granularity gap.
Establishes the overarching access-control policy whose granularity directly determines whether the weakness exists.
Defines the assignment and review of access rights; insufficient granularity in those rights is the root of CWE-1220.
Specifies management of privileged access rights, where overly broad privileges are a common manifestation of the weakness.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Windows Server 2016 (1 rule)
- V-225025 Local accounts with blank passwords must be restricted to prevent access from the network. prevents CWE-1220
Windows Server 2022 (1 rule)
- V-254446 Windows Server 2022 must prevent local accounts with blank passwords from being used from the network. prevents CWE-1220