# CVE-2026-62429: vNUMA domain cleanup may race other operations

> A race condition in Xen's vNUMA cleanup allows device models to access destroyed domain data, potentially causing crashes or undefined behavior.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** ALPINE-CVE-2026-62429, DEBIAN-CVE-2026-62429, GHSA-8fgv-987v-pg9v, UBUNTU-CVE-2026-62429

## What is CVE-2026-62429?

CVE-2026-62429 is a medium-severity vulnerability in Xen, published on 28 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Accessing the vNUMA configuration data of a guest is still possible when
domain destruction has already started.  The cleaning up of that
configuration information is not synchronized with its retrieval by a
device model controlling the guest.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-62429?


## How do I fix CVE-2026-62429?

Apply the vendor's patch.

## Is CVE-2026-62429 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62429 and fix it if it is affected.

What it is: CVE-2026-62429 is a medium-severity vulnerability in Xen, published on 28 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62429 in the wild and no public exploit code.

Affected product: Xen. 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-2026-62429/ (Markdown: https://insights.sbomify.com/CVE-2026-62429/index.md)
```

## Sources

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

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