# CVE-2026-62437: x86: DMs may cause mem leak by IRQ binding

> A race condition in Xen allows a guest to cause a memory leak by re-binding IRQs during termination, potentially leading to denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** ALPINE-CVE-2026-62437, DEBIAN-CVE-2026-62437, GHSA-vfxv-3qcw-g966, UBUNTU-CVE-2026-62437

## What is CVE-2026-62437?

CVE-2026-62437 is a medium-severity vulnerability in Xen, published on 8 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

When guests are terminated, various pieces of cleanup need carrying out.
The cleaning up of PCI devices which were assigned to guests, and the
associated removal of tracking structures for IRQs used by the devices
occurs relatively early in the process.  Unfortunately after that point
the guest about to be terminated could cause its device model (DM) to
re-establish such tracking structures, by having it bind one or more IRQs
anew.  While some of those tracking structures would still be cleaned up
later on, at least one would not be.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-62437 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62437 is a medium-severity vulnerability in Xen, published on 8 Sep 2026. 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-2026-62437 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-62437/ (Markdown: https://insights.sbomify.com/CVE-2026-62437/index.md)
```

## Sources

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

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