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.
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.
Project Subscriptions
No data.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
Running only PV or PVH guests will avoid the vulnerability. Running only HVM guests without passing through PCI devices to them will also avoid the vulnerability.
References
| Link | Providers |
|---|---|
| https://xenbits.xenproject.org/xsa/advisory-509.html |
|
History
Tue, 08 Sep 2026 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-391 |
Tue, 08 Sep 2026 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | x86: DMs may cause mem leak by IRQ binding | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: XEN
Published:
Updated: 2026-09-08T13:08:02.579Z
Reserved: 2026-07-14T10:28:12.655Z
Link: CVE-2026-62437
No data.
Status : Received
Published: 2026-09-08T13:17:19.623
Modified: 2026-09-08T13:17:19.623
Link: CVE-2026-62437
No data.
OpenCVE Enrichment
Updated: 2026-09-08T13:30:18Z
Weaknesses