dbcve.org
Amd UprofApplication · Amd

CVE-2022-23831

HIGH · 7.5 CVSS v3.1 Published 2022-11-09
Fix available
A fix is available. Upgrade to 3.6.449 / 3.6.549 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Insufficient validation of the IOCTL input buffer in AMD μProf may allow an attacker to send an arbitrary buffer leading to a potential Windows kernel crash resulting in denial of service.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

AMD μProf driver has insufficient validation of IOCTL input buffers, allowing an attacker to send arbitrary buffers that can trigger a Windows kernel crash and cause denial of service.

MitigationApply vendor-supplied patches for AMD μProf when available; until patched, restrict access to the profiling driver and monitor for anomalous IOCTL requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Amd UprofApplication
Affected:< 3.6.549< 3.6.839< 3.6.449

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify AMD μProf installation
    Open Programs and Features in Control Panel or use 'Get-ItemProperty' in PowerShell for registry key HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\* to locate AMD μProf
    Affected if AMD μProf is listed as installed software on the system
  2. Retrieve installed AMD μProf version
    In PowerShell, run 'Get-ItemProperty' against the AMD μProf installation directory (commonly C:\Program Files\AMD\uProf) or check the file version of the main executable such as uProf.exe
    Affected if The version shown is less than 3.6.549, less than 3.6.839, or less than 3.6.449 depending on the installed branch
  3. Confirm driver presence
    Open Device Manager, look under 'System devices' or check the Windows driver file associated with AMD μProf (commonly in the installation directory with .sys extension)
    Affected if The AMD μProf kernel driver file exists on the system
  4. Check if profiling driver is loaded
    Run 'sc query amduprof' or 'sc query type= driver' in Command Prompt and filter for AMD-related profiling drivers
    Affected if The driver service exists and is running, meaning the vulnerable IOCTL interface is active

The system is affected if AMD μProf is installed with a version lower than 3.6.549, 3.6.839, or 3.6.449 (depending on the version branch) and the profiling driver is loaded and active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.6.449 / 3.6.549 / 3.6.839 or later
Fixed in 3.6.4493.6.5493.6.839
Interim mitigation

Apply vendor-supplied patches for AMD μProf when available; until patched, restrict access to the profiling driver and monitor for anomalous IOCTL requests.

Recommended fix Moderate confidence

AMD μProf version 3.6.549 or later

  1. 1. Identify the currently installed AMD μProf version via 'amd-uprof --version' or the application's About/Help section
  2. 2. Download AMD μProf version 3.6.549 or higher from the official AMD website (developer.amd.com/developer-tools/amd-uprof)
  3. 3. Close any running AMD μProf instances and associated services
  4. 4. Uninstall the current AMD μProf version through Windows Add/Remove Programs
  5. 5. Run the installer for the new version (3.6.549 or higher) with administrator privileges
  6. 6. Follow the installation wizard prompts and restart the system if prompted
  7. 7. Verify the installation succeeded and confirm the new version matches or exceeds 3.6.549
Caveat Review AMD release notes for any deprecated features or compatibility changes between your current version and 3.6.x

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Amd Uprof Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23831 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-23831 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data