Cyber Resilience

CVE-2025-48511

Amd Uprof ≤ 5.0.1174

Published
24 November 2025
Modified
26 November 2025
Patch / advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0011 1th percentile
Risk Priority 40 floored blend · peak EPSS

Summary

CVE-2025-48511 is a medium-severity Improper Validation of Specified Index, Position, or Offset in Input (CWE-1285) vulnerability in Amd Uprof. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 1th 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Improper input validation within AMD uprof can allow a local attacker to write to an arbitrary physical address, potentially resulting in crash or denial of service.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-48502Same product: Amd Uprof
CVE-2025-29933Same product: Amd Uprof
CVE-2023-31366Same product: Amd Uprof
CVE-2023-31341Same product: Amd Uprof
CVE-2023-31348Same product: Amd Uprof
CVE-2023-31349Same product: Amd Uprof
CVE-2024-36340Same product: Amd Uprof
CVE-2026-0466Same product: Amd Uprof
CVE-2025-48510Same product: Amd Uprof
CVE-2023-20519Same vendor: Amd

Affected Assets

amd
uprof
≤ 5.0.1174 · ≤ 5.0.1223 · ≤ 5.0.1479

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.4.2
  • V2.1.1
  • V2.2.1
  • V2.2.2

Mitigating Controls (NIST 800-53 r5) AI

Requires explicit validation of supplied indices/offsets/positions before they are used to access buffers or other indexable resources.

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.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation, preventing this class of flaw at development time.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover missing index validation via scanning or reviews.

PR.PS-02 partial match
prevents

Patching and replacement can remediate instances of the weakness after discovery.

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.

finds

Security testing can detect missing or incorrect index validation during development and acceptance.

prevents

Secure development lifecycle includes input validation requirements that can prevent improper index handling.

prevents

Application security requirements typically mandate bounds checking and validation of offsets/indices.

prevents

Secure architecture principles include defensive input validation and bounds checking for indexable resources.

prevents

Secure coding standards directly require validation of indices, positions, and offsets before use.

References