AZL-114902: CVE-2026-99453 affecting package kernel 6.6.161.1-1
In the Linux kernel, the following vulnerability has been resolved:
xen-blkfront: unbind irq before tearing down ring and shadow requests
In blkiffreering(), the driver tears down the ring's persistent grants, shadow request arrays, and shared ring structure (xenbusteardownring), and only calls unbindfromirqhandler() at the very end.
While blkiffreering() is freeing persistent grants and clearing the shadow array, the event channel interrupt (blkifinterrupt) is still registered and active. If an interrupt arrives from the backend during this teardown window, blkifinterrupt() reads rinfo->ring.sring and, via blkifcompletion(), accesses rinfo->shadow[id].grantsused and rinfo->shadow[id].sg. blkiffreering() tears these structures down without holding rinfo->ringlock, and the handler only checks info->connected at entry, so this is a real race resulting in a use-after-free or NULL pointer dereference.
Fix this by moving unbindfromirqhandler() to the beginning of blkiffreering(). Calling unbindfromirqhandler() first frees the IRQ and synchronizes with any in-flight interrupt handlers on other CPUs before ring memory and shadow request structures are deallocated, matching the teardown order in drivers/net/xen-netfront.c.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
In blkif_free_ring(), call unbind_from_irqhandler() at the beginning, before tearing down persistent grants, ring memory, and shadow request structures, so in-flight interrupt handlers are synchronized before those structures are freed.