CVE-2025-24084
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 · uneditedUntrusted pointer dereference in Windows Subsystem for Linux allows an unauthorized attacker to execute code 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 confidenceUntrusted pointer dereference vulnerability in Windows Subsystem for Linux allows a local attacker to execute arbitrary code by controlling or corrupting memory through improper pointer validation in WSL 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< 10.0.22621.5039< 10.0.22631.5039< 10.0.26100.3403< 10.0.20348.3270< 10.0.25398.1486< 10.0.26100.3403CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WSL is installed or enabledRun 'wsl --status' in Command Prompt or PowerShell, or check Windows Features for 'Windows Subsystem for Linux' via OptionalFeatures.exeAffected if WSL is installed or enabled on the system - the vulnerability only applies when WSL is present
-
Check Windows build versionRun 'winver' or execute 'systeminfo | findstr /B /C:"OS Version"' in Command PromptAffected if The Windows build number is lower than 10.0.22621.5039 (22h2), 10.0.22631.5039 (23h2), 10.0.26100.3403 (24h2/Server 2025), 10.0.20348.3270 (Server 2022), or 10.0.25398.1486 (Server 2022 23h2)
-
Confirm WSL kernel version from within LinuxOpen any WSL distribution and run 'cat /proc/version' or run 'wsl --version' from Windows command lineAffected if The WSL kernel version corresponds to an unpatched Windows build as identified in step 2
You are affected if WSL is installed/enabled AND your Windows build version falls below the fixed version numbers listed for your Windows edition.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.20348.327010.0.22621.503910.0.22631.5039
Apply Microsoft security updates for Windows Subsystem for Linux through Windows Update to patch the memory handling flaw.
Install Windows security update KB500xxxx (specific KB number from Microsoft Security Response Center for CVE-2025-24084) to reach fixed build versions as listed above
- Open Windows Settings and navigate to Windows Update
- Check for updates and install all available updates, or manually download and install the specific KB security update for your Windows version from Microsoft Update Catalog
- Restart your system after installing the update
- Verify the update was installed successfully by checking Windows version/build number matches or exceeds the fixed build: Windows 11 22h2: 10.0.22621.5039, Windows 11 23h2: 10.0.22631.5039, Windows 11 24h2: 10.0.26100.3403, Windows Server 2022: 10.0.20348.3270, Windows Server 2022 23h2: 10.0.25398.1486, Windows Server 2025: 10.0.26100.3403
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-24084 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24084 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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