Answer in brief
CVE-2026-98564 records a Unknown severity vulnerability in net: dsa: mt7530: leave the MDIO IRQ mappings to regmap-irq. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=254f6b272e3b67bf31c42ee9da62a449d74d1478 <2357c682f6eaf639dec88c68b3c0c93a3b802635 || >=254f6b272e3b67bf31c42ee9da62a449d74d1478 <f306e465b5a2091cd3fe3dd0feb10cfc94cfb2f8 || >=254f6b272e3b67bf31c42ee9da62a449d74d1478 <0d80ba0a204c6a16bd7778b50de578dff107c0fe | 2357c682f6eaf639dec88c68b3c0c93a3b802635, f306e465b5a2091cd3fe3dd0feb10cfc94cfb2f8, 0d80ba0a204c6a16bd7778b50de578dff107c0fe |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.