CVE-2026-98564 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, as well as users who rely on the mt7530 driver, should review and apply the patches provided by the Linux kernel maintainers to prevent potential issues. Affected operator, platform, vulnerability-management, and security-team impact should be assessed to ensure proper mitigation.

Why it matters

A vulnerability in the Linux kernel has been resolved, related to the mt7530 driver. The issue arises from the improper disposal of per-PHY interrupt mappings in the .remove function, which can lead to a fault when the regmap-irq thread dispatches on a mapping that is already gone. Linux kernel developers and maintainers should review and apply the patches provided by the Linux kernel maintainers to prevent potential issues.

• Potential system crashes or instability due to the fault.
• Possible security risks if the vulnerability is exploited.
• Need for patching and updating the Linux kernel to prevent potential issues.

Technical summary

The vulnerability is related to the mt7530 driver in the Linux kernel. The issue arises from the improper disposal of per-PHY interrupt mappings in the .remove function, which can lead to a fault when the regmap-irq thread dispatches on a mapping that is already gone. 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, potentially causing system crashes or instability.

Defensive priority

Medium

Recommended defensive actions

• Review and apply the patches provided by the Linux kernel maintainers.
• Ensure that the Linux kernel is updated to the latest version.
• Monitor the system for any potential issues related to the mt7530 driver.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The vulnerability is related to the mt7530 driver in the Linux kernel. The issue is caused by the improper disposal of per-PHY interrupt mappings in the .remove function. 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.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.