# CVE-2024-10972: WinPmem Improper Input Validation vulnerability

> An attacker with admin access can cause a Blue Screen of Death in WinPmem by exploiting a race condition in memory permission checks.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2024
- **Updated:** 5 Sep 2025
- **Also known as:** GHSA-q5vw-gwwh-j8r7

## What is CVE-2024-10972?

CVE-2024-10972 is a high-severity vulnerability in Velocidex WinPmem, published on 16 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Velocidex WinPmem versions 4.1 and below suffer from an Improper Input Validation vulnerability whereby an attacker with admin access can trigger a BSOD with a parallel thread changing the memory’s access right under the control of the user-mode application. This is due to verification only being performed at the beginning of the routine allowing the userspace to change page permissions half way through the routine.  A valid workaround is a rule to detect unauthorized loading of winpmem outside incident response operations.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2024-10972?


## How do I fix CVE-2024-10972?

No fix has been published for CVE-2024-10972 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-10972 being exploited?

There is no known exploitation of CVE-2024-10972 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10972 and fix it if it is affected.

What it is: CVE-2024-10972 is a high-severity vulnerability in Velocidex WinPmem, published on 16 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10972 in the wild and no public exploit code.

Affected product: Velocidex WinPmem. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-10972/ (Markdown: https://insights.sbomify.com/CVE-2024-10972/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-10972
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-10972
- OSV: https://osv.dev/vulnerability/CVE-2024-10972

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-10972/
Summaries are generated and may contain mistakes; the official description above is the record.