CVE-2026-62437: x86: DMs may cause mem leak by IRQ binding
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.
Affected Software
Event History
Frequently Asked Questions
What must an attacker or guest be able to do to trigger the issue?
The guest must be in the process of termination and be able to cause its device model to bind one or more IRQs again after early PCI-device and IRQ-tracking cleanup has occurred.
Which environments are implicated by the described cleanup path?
The affected path involves guests with assigned PCI devices and the IRQ tracking structures associated with those devices. A device model must be able to re-establish IRQ bindings during guest teardown.