dbcve.org
Windows 11 22h2Operating system · Microsoft

CVE-2025-29812

HIGH · 7.8 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.20348.3453 / 10.0.22621.5189 or later.
See remediation →
80/100
Remediation priority · High
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
Untrusted pointer dereference in Windows Kernel Memory allows an authorized attacker to elevate privileges 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 · moderate confidence

A flaw exists in Windows Kernel Memory handling where an untrusted pointer is dereferenced, allowing a locally authenticated attacker to execute code at elevated (kernel) privilege levels. The vulnerability stems from improper validation of memory pointers within kernel-space operations, enabling arbitrary code execution in the most privileged CPU mode.

MitigationApply Microsoft security updates for CVE-2025-29812 immediately; prioritize systems with direct user access. Until patches are available, limit local administrative privileges and monitor for suspicious kernel-mode driver activity.

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 11 22h2Operating system
Affected:< 10.0.22621.5189
Windows 11 23h2Operating system
Affected:< 10.0.22631.5189
Windows 11 24h2Operating system
Affected:< 10.0.26100.3775
Windows Server 2022Operating system
Affected:< 10.0.20348.3453
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1551
Windows Server 2025Operating system
Affected:< 10.0.26100.3775

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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Check Windows build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number
    Affected if The build number falls below the fixed versions: 22621.5189 (Win11 22h2), 22631.5189 (Win11 23h2), 26100.3775 (Win11 24h2/Server 2025), 20348.3453 (Server 2022), 25398.1551 (Server 2022 23h2)
  2. Identify exact Windows edition
    Run 'winver' or check System Properties to confirm whether the system is Windows 11 (22h2, 23h2, or 24h2) or Windows Server (2022, 2022 23h2, or 2025)
    Affected if The installed edition matches one of the affected products listed in the CVE but the build number is below the corresponding fixed version
  3. Confirm patch installation status
    Run 'wmic qfe list' or check Windows Update history for security updates installed after the CVE release date
    Affected if The KB corresponding to CVE-2025-29812 (check Microsoft Security Response Center for the specific KB number) is not installed

A system is affected if it runs a Windows 11 or Windows Server edition matching the listed versions AND its build number is below the specified threshold for that edition.

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.20348.3453 / 10.0.22621.5189 / 10.0.22631.5189 or later
Fixed in 10.0.20348.345310.0.22621.518910.0.22631.5189
Interim mitigation

Apply Microsoft security updates for CVE-2025-29812 immediately; prioritize systems with direct user access. Until patches are available, limit local administrative privileges and monitor for suspicious kernel-mode driver activity.

Recommended fix High confidence

June 2025 Windows Security Update (KB506xxxx series - specific KB varies by Windows version)

  1. Open Windows Update on the affected system
  2. Check for available updates and ensure the June 2025 security updates are installed
  3. For Windows 11 22h2: install update building to 10.0.22621.5189 or later
  4. For Windows 11 23h2: install update building to 10.0.22631.5189 or later
  5. For Windows 11 24h2: install update building to 10.0.26100.3775 or later
  6. For Windows Server 2022: install update building to 10.0.20348.3453 or later
  7. For Windows Server 2022 23h2: install update building to 10.0.25398.1551 or later
  8. For Windows Server 2025: install update building to 10.0.26100.3775 or later
Caveat Standard Windows security update - no expected breaking changes for most configurations; test in staging if concerned

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

Fix this in Windows 11 22h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,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 $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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