CVE-2026-98564

In the Linux kernel, the following vulnerability has been resolved:

net: dsa: mt7530: leave the MDIO IRQ mappings to regmap-irq

mt7530 remove common() disposes the per-PHY interrupt mappings from .remove, but the regmap-irq chip that owns the domain is devm-registered, so its parent interrupt is only freed once .remove has returned. The switch's own regmap-irq thread can therefore still dispatch on a mapping that is already gone: irq find mapping() returns 0, irq to desc() returns NULL and handle nested irq() locks desc->lock without checking it. The attached PHYs have not given those interrupts back yet either, which the kernel warns about a moment before the fault.

regmap del irq chip() disposes the same mappings itself, after freeing the parent interrupt and before removing the domain, so there is nothing left for the driver to do here. Until it runs the descriptors stay alive, and a late dispatch on one of them is harmless: dsa unregister switch() has freed the PHY handlers by then, so handle nested irq() finds no action and returns.