CVE-2025-29933VulnerabilityPublished 24 Nov 2025

CVE-2025-29933: AMD μProf · Out-of-bounds Write

Affects AMD μProfSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Organizations should restrict access to AMD μProf to trusted users only, employing strict access controls and monitoring local user activities. Until patches are released, consider limiting installation of AMD μProf to essential systems and avoid running it on critical production machines. Employ endpoint detection and response (EDR) solutions to detect abnormal application crashes or suspicious local activity. Regularly update AMD μProf and related AMD software components as vendor patches become available. Conduct internal audits to identify systems with AMD μProf installed and assess exposure. Implement least privilege principles to reduce the number of users who can execute profiling tools. Additionally, consider isolating development and profiling environments from sensitive production networks to contain potential denial of service impacts. Maintain up-to-date backups and incident response plans to quickly recover from any disruption caused by exploitation.

Description

CVE-2025-29933 is a medium severity vulnerability in AMD μProf caused by improper input validation leading to an out-of-bounds write. This flaw allows a local attacker with limited privileges to write outside intended memory bounds, potentially causing application crashes or denial of service. The vulnerability does not impact confidentiality or integrity but affects availability. Exploitation requires local access and no user interaction, limiting remote attack feasibility. No known exploits are currently reported in the wild. European organizations using AMD μProf for performance profiling on AMD processors may be affected, especially in sectors relying on AMD hardware for development or performance analysis. Mitigations include restricting local access to AMD μProf, applying vendor patches when available, and monitoring for abnormal application behavior. Countries with significant AMD hardware adoption and strong tech sectors, such as Germany, France, and the UK, are more likely to be impacted. Overall, this vulnerability poses a moderate risk primarily through denial of service scenarios in local environments.

Impact

For European organizations, the primary impact is denial of service on systems running AMD μProf, potentially disrupting performance analysis and development activities. This could delay troubleshooting or optimization efforts in IT departments or product development teams relying on AMD hardware profiling. While the vulnerability does not expose sensitive data or allow privilege escalation, the availability impact could affect operational efficiency, especially in technology companies, research institutions, or sectors with heavy AMD hardware usage. Organizations with strict uptime requirements or those using automated profiling in production-like environments may experience workflow interruptions. The requirement for local access limits the risk of widespread remote attacks but insider threats or malware with local access could exploit this vulnerability. The lack of known exploits reduces immediate risk, but unpatched systems remain vulnerable to potential future attacks.

Summary

CVE-2025-29933 is an out-of-bounds write vulnerability classified under CWE-787 found in AMD μProf, a performance profiling tool used on AMD processors. The root cause is improper input validation that allows a local attacker with limited privileges to write data beyond allocated memory boundaries. This memory corruption can lead to application instability, crashes, or denial of service conditions. The vulnerability requires local access and does not necessitate user interaction, meaning an attacker must already have some level of access to the system. The CVSS 3.1 base score is 5.5 (medium severity), reflecting the limited scope and impact confined to availability without affecting confidentiality or integrity. No known exploits have been reported in the wild, and no patches have been linked yet, indicating this is a recently disclosed issue. AMD μProf is primarily used by developers and performance engineers to analyze processor performance, so the attack surface is limited to environments where this tool is installed and used. The vulnerability could be exploited by malicious local users or malware that gains local foothold to disrupt profiling activities or cause denial of service. Given the nature of the tool, this vulnerability is less likely to be exploited remotely but could impact development or diagnostic workflows.

CWE-787Out-of-bounds Write (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #5
The product writes data past the end, or before the beginning, of the intended buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

amd.com/en/resources/product-security/bulletin/AMD-SB-9019.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 1 Dec 2025, 21:39 UTC

WeaknessesCWE-787

Technical details

References

Community reviews

Related threats