CVE-2025-0036
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:NSummary
CVE-2025-0036 is a low-severity Exposure of Sensitive System Information to an Unauthorized Control Sphere (CWE-497) vulnerability in Amd (inferred from references). Its CVSS base score is 3.2 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique ARP Cache Poisoning (T1557.002); ranked at the 3th 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-17 (Remote Access) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-17610
Vulnerability Data
In AMD Versal Adaptive SoC devices, the incorrect configuration of the SSS during runtime (post-boot) cryptographic operations could cause data to be incorrectly written to and read from invalid locations as well as returning incorrect cryptographic data.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 5 hardening rules · 4 OS baselines
V14.1.2V15.2.2V3.5.3V10.6.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces approved authorizations for logical access, directly stopping unauthorized actors from reaching sensitive system information.
IA-3 requires unique identification and authentication of devices before any communication channel is established, directly stopping acceptance of unverified origins.
AC-17 mandates documented restrictions and authentication requirements for remote access, blocking channels whose origins are not properly verified.
Enforces information flow policies that block sensitive system data from crossing into unauthorized control spheres.
Limits privileges so that only the minimum necessary access is granted, reducing the chance of exposing system-level details.
Developer testing and evaluation directly exercises calculations and can discover incorrect or unintended results used in security decisions.
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.
Authentication of users/services/hardware directly enforces source verification for communication channels.
Lifecycle management explicitly requires handling resources through end-of-life including release.
Verifying identity assertions prevents spoofed channel origins but does not cover all channel-establishment scenarios.
Enforcing least-privilege access permissions directly prevents unauthorized actors from reaching sensitive system information.
Protecting environments from unauthorized logical access stops exposure of internal system details to outsiders.
Hardened configuration baselines and change control prevent mis-specified endpoints from being deployed.
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.
Explicit information-deletion requirements directly address timely release of resources after use.
Security testing in development and acceptance can detect calculation flaws before deployment.
Secure authentication mechanisms verify the identity and origin of communication channel initiators.
Network security controls enforce source verification and channel authentication for incoming communications.
Security of network services includes validating the origin of service requests and connections.
Network segregation limits exposure but does not directly verify source of individual channels.
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).
Oracle Linux 8 (2 rules)
- V-248551 A sticky bit must be set on all OL 8 public directories to prevent unauthorized and unintended information transferred via shared system resources. prevents CWE-497
- V-248580 OL 8 must prevent kernel profiling by unprivileged users. prevents CWE-497
RHEL 8 (1 rule)
- V-230270 RHEL 8 must prevent kernel profiling by unprivileged users. prevents CWE-497
Ubuntu 22.04 (1 rule)
- V-260470 Ubuntu 22.04 LTS, when booted, must require authentication upon booting into single-user and maintenance modes. prevents CWE-497
Ubuntu 24.04 (1 rule)
- V-270675 Ubuntu 24.04 LTS when booted must require authentication upon booting into single-user and maintenance modes. prevents CWE-497