dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-29829

MEDIUM · 5.5 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 10.0.10240.21014 / 10.0.14393.8066 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Use of uninitialized resource in Windows Trusted Runtime Interface Driver allows an authorized attacker to disclose information locally.

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 · high confidence

The Windows Trusted Runtime Interface Driver contains a use of uninitialized resource vulnerability. When the driver handles certain operations, it fails to properly initialize a resource (likely memory) before using it, allowing a locally authorized attacker to read potentially sensitive uninitialized data from memory.

MitigationApply the Microsoft security update for CVE-2025-29829 through Windows Update or enterprise patch management systems to remediate the vulnerability in the Trusted Runtime Interface Driver.

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
Windows 10 1507Operating system
Affected:< 10.0.10240.21014
Windows 10 1607Operating system
Affected:< 10.0.14393.8066
Windows 10 1809Operating system
Affected:< 10.0.17763.7314
Windows 10 21h2Operating system
Affected:< 10.0.19044.5854
Windows 10 22h2Operating system
Affected:< 10.0.19045.5854
Windows 11 22h2Operating system
Affected:< 10.0.22621.5335
Windows 11 23h2Operating system
Affected:< 10.0.22631.5335
Windows 11 24h2Operating system
Affected:< 10.0.26100.4061

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Check Windows build version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number
    Affected if The build number falls below any of these thresholds: 10240.21014 (Win10 1507), 14393.8066 (Win10 1607), 17763.7314 (Win10 1809), 19044.5854 (Win10 21h2), 19045.5854 (Win10 22h2), 22621.5335 (Win11 22h2), 22631.5335 (Win11 23h2), 26100.4061 (Win11 24h2)
  2. Verify Trusted Runtime Interface Driver presence
    Open Command Prompt as Administrator and run 'sc query trkwks' or check for the driver file in System32\drivers folder
    Affected if The driver service exists (trkwks) on the system indicating the Trusted Runtime Interface Driver is installed
  3. Check driver file version
    Locate the driver file (typically trkwks.sys in C:\Windows\System32\drivers) and right-click > Properties > Details to view the File Version, or use 'driverquery /v | findstr trkwks'
    Affected if The driver file version is present and the underlying Windows build is below the patched versions listed above
  4. Confirm driver loaded status
    Run 'sc query trkwks' or check Device Manager for any Trusted Runtime Interface devices under System devices
    Affected if The driver is in a running state (SERVICE_RUNNING) which would be required to exploit the vulnerability
  5. Check for recent security patches
    Open Control Panel > Programs > Programs and Features > View installed updates, or run 'wmic qfe list' to see installed hotfixes
    Affected if No Microsoft security update for CVE-2025-29829 is listed among installed updates

The system is affected if it runs a Windows version with a build number lower than the thresholds listed above AND has the Trusted Runtime Interface Driver (trkwks) present and potentially 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 10.0.10240.21014 / 10.0.14393.8066 / 10.0.17763.7314 or later
Fixed in 10.0.10240.2101410.0.14393.806610.0.17763.7314
Interim mitigation

Apply the Microsoft security update for CVE-2025-29829 through Windows Update or enterprise patch management systems to remediate the vulnerability in the Trusted Runtime Interface Driver.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21014 | Windows 10 1607: 10.0.14393.8066 | Windows 10 1809: 10.0.17763.7314 | Windows 10 21h2: 10.0.19044.5854 | Windows 10 22h2: 10.0.19045.5854 | Windows 11 22h2: 10.0.22621.5335 | Windows 11 23h2: 10.0.22631.5335 | Windows 11 24h2: 10.0.26100.4061

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click Check for updates to download and install the latest security updates
  3. Ensure the update includes the patch for CVE-2025-29829 (Windows Trusted Runtime Interface Driver)
  4. After installation, verify the build number matches or exceeds the fixed version for your Windows release
  5. Restart the system if prompted to complete the installation
Caveat Standard Windows update - no breaking changes expected for this informational disclosure vulnerability patch

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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