Skip to content
Threat Brief

← All advisories

CVE-2026-99453

Severity unknownNo known exploitationFix available

xen-blkfront: unbind irq before tearing down ring and shadow requests

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 7% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 11659569f7202d0cb6553e81f9b8aa04dfeb94ce before e64707d07fcda07c71d4f1405c1bedb0787a6889e64707d07fcda07c71d4f1405c1bedb0787a6889CVE Program
LinuxLinuxfrom 11659569f7202d0cb6553e81f9b8aa04dfeb94ce before 5f4b2debc87b6f86b56c6e1f5d97007a330d6aac5f4b2debc87b6f86b56c6e1f5d97007a330d6aacCVE Program
LinuxLinuxfrom 11659569f7202d0cb6553e81f9b8aa04dfeb94ce before f3e27b7955727a4d7c0e9264a2a209fbba788bdcf3e27b7955727a4d7c0e9264a2a209fbba788bdcCVE Program
LinuxLinuxfrom 11659569f7202d0cb6553e81f9b8aa04dfeb94ce before 9cdf4fae8fde297ed9ce6bb0058d25449606ee669cdf4fae8fde297ed9ce6bb0058d25449606ee66CVE Program
LinuxLinux4.5Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.117 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.61 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.2 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 4.5Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references