PT-2026-151664
CVE-2026-99453
·
Publicado
2026-11-19
·
Atualizado
2026-11-19
Descrição por
Pontuação
N/A
Não disponívelNão há classificações de severidade ou métricas disponíveis. Quando houver, atualizaremos as informações correspondentes na página.
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.
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾