Improper input validation within AMD uprof can allow a local attacker to write to an arbitrary physical address
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 17 Nov 2026, 01:43 UTC
Thin evidence
One scorer or none| CNA (AMD) | CVSS 3.1 | 5.5 |
|---|
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
AI-suggested
Until a fix is available, restrict local access to trusted users only.
Description
A vulnerability in AMD uprof due to improper input validation allows a local attacker to write to an arbitrary physical address. This can lead to system crashes or denial of service conditions. The vulnerability does not impact confidentiality or integrity but affects availability.