CVE-2026-99453
xen-blkfront: unbind irq before tearing down ring and shadow requests
What happened?
In the Linux kernel, the following vulnerability has been resolved:
xen-blkfront: unbind irq before tearing down ring and shadow requests
In blkif_free_ring(), the driver tears down the ring's persistent grants, shadow request arrays, and shared ring structure (xenbus_teardown_ring), and only calls unbind_from_irqhandler() at the very end.
While blkif_free_ring() is freeing persistent grants and clearing the shadow array, the event channel interrupt (blkif_interrupt) is still registered and active. If an interrupt arrives from the backend during this teardown window, blkif_interrupt() reads rinfo->ring.sring and, via blkif_completion(), accesses rinfo->shadow[id].grants_used and rinfo->shadow[id].sg. blkif_free_ring() tears these structures down without holding rinfo->ring_lock, 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 unbind_from_irqhandler() to the beginning of blkif_free_ring(). Calling unbind_from_irqhandler() 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 and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 11659569f7202d0cb6553e81f9b8aa04dfeb94ce to < 9cdf4fae8fde297ed9ce6bb0058d25449606ee66; affected: 11659569f7202d0cb6553e81f9b8aa04dfeb94ce to < e64707d07fcda07c71d4f1405c1bedb0787a6889; affected: 11659569f7202d0cb6553e81f9b8aa04dfeb94ce to < 5f4b2debc87b6f86b56c6e1f5d97007a330d6aac; affected: 11659569f7202d0cb6553e81f9b8aa04dfeb94ce to < f3e27b7955727a4d7c0e9264a2a209fbba788bdc | See vendor advisory |
| LinuxLinux | affected: 4.5; unaffected: 0 to < 4.5; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99453
- https://git.kernel.org/stable/c/9cdf4fae8fde297ed9ce6bb0058d25449606ee66
- https://git.kernel.org/stable/c/e64707d07fcda07c71d4f1405c1bedb0787a6889
- https://git.kernel.org/stable/c/5f4b2debc87b6f86b56c6e1f5d97007a330d6aac
- https://git.kernel.org/stable/c/f3e27b7955727a4d7c0e9264a2a209fbba788bdc