dbcve.org
Amd UprofApplication · Amd

CVE-2022-27674

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 in the IOCTL input/output buffer in AMD μProf may allow an attacker to bypass bounds checks potentially leading to a 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

Insufficient validation in the IOCTL input/output buffer handling in AMD μProf allows an attacker to bypass bounds checks. This occurs when the profiling tool's driver or component processes IOCTL requests without properly validating buffer sizes or ranges, potentially triggering a Windows kernel crash leading to denial of service.

MitigationApply the vendor-supplied patch for AMD μProf. Until patched, restrict access to untrusted users and monitor for indicators of exploitation targeting the profiling tool's driver components.

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
    Check for AMD μProf installation by looking in Program Files for the AMD uProf directory, or use registry key HKLM\SOFTWARE\WOW6432Node\AMD\uProf or check Programs and Features in Control Panel
    Affected if AMD μProf is installed on the system
  2. Locate the installed version
    Open the AMD μProf installation directory (typically C:\Program Files\AMD\uProf or C:\Program Files (x86)\AMD\uProf) and locate the version information in the file properties, or run 'uProf Version' from command line if the tool is in PATH
    Affected if Unable to determine the version number from the installation
  3. Compare version against affected ranges
    Compare the installed version number to the affected thresholds: < 3.6.449, < 3.6.549, and < 3.6.839. Note that different minor builds may fall into different branch ranges, so check if your version is lower than ANY of these three thresholds
    Affected if Installed version is lower than 3.6.449, or between 3.6.449-3.6.549, or between 3.6.549-3.6.839, depending on which branch your build belongs to
  4. Identify the profiling driver component
    Check for the presence of the AMD μProf driver files in the system: look for files named 'AmdUProf.sys' or similar driver components in the Windows System32\drivers folder or within the AMD μProf installation directory
    Affected if The profiling driver component is present on the system

The system is affected if AMD μProf is installed with a version lower than 3.6.839 (the highest patched threshold) and the profiling driver component is present and loaded.

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 the vendor-supplied patch for AMD μProf. Until patched, restrict access to untrusted users and monitor for indicators of exploitation targeting the profiling tool's driver components.

Recommended fix Moderate confidence

AMD μProf version 3.6.549 or higher

  1. 1. Visit the official AMD website at www.amd.com to download the latest AMD μProf version
  2. 2. Navigate to the AMD μProf download page or support section
  3. 3. Download the latest stable release of AMD μProf (version 3.6.549 or higher)
  4. 4. Close any running instances of AMD μProf
  5. 5. Run the installer and follow the on-screen instructions to update the software
  6. 6. Restart the system if prompted to ensure all components are properly updated
  7. 7. Verify the installed version matches or exceeds the fixed release (3.6.549)

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

Fix this in Amd Uprof Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27674 — 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-27674 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