Skip to main content

In the Linux kernel, the following vulnerability has been resolved: net: dsa: mt7530: leave the MDIO IRQ mappings to regmap-irq… (CVE-2026-98564)

0
Medium
Published: 10/18/2026 (10/18/2026, 18:31:54 UTC)
Source: GCVE Database

Description

A vulnerability in the Linux kernel's net: dsa: mt7530 driver involves improper handling of MDIO IRQ mappings. The issue arises because the regmap-irq chip that owns the interrupt domain is devm-registered and its parent interrupt is only freed after the .remove function returns. This can lead to the switch's regmap-irq thread dispatching on an already removed mapping, causing a fault due to a NULL descriptor lock. The vulnerability has been resolved by leaving the MDIO IRQ mappings to regmap-irq to manage properly.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/18/2026, 20:49:24 UTC

Technical Analysis

The vulnerability in the Linux kernel's mt7530 driver concerns the disposal of per-PHY interrupt mappings during the removal process. The driver disposes these mappings in mt7530_remove_common(), but since the regmap-irq chip is devm-registered, its parent interrupt is freed only after .remove returns. This timing allows the regmap-irq thread to dispatch interrupts on mappings that have been removed, leading to a NULL pointer dereference in handle_nested_irq() due to locking a NULL descriptor. The fix involves leaving the MDIO IRQ mappings management to regmap-irq itself, which properly disposes of the mappings after freeing the parent interrupt, preventing late dispatch faults.

Potential Impact

The vulnerability can cause a kernel fault due to a NULL pointer dereference when the regmap-irq thread dispatches on an already removed interrupt mapping. This may lead to instability or crashes in the affected Linux kernel versions running the mt7530 driver. However, the fault occurs after the PHY handlers have been freed, so no further action is taken by handle_nested_irq(), limiting the impact to a potential kernel fault or crash.

Mitigation Recommendations

A fix has been implemented in the Linux kernel to resolve this issue by delegating the MDIO IRQ mappings management to regmap-irq, which properly frees the parent interrupt and removes the domain in the correct order. Users should update to the fixed Linux kernel version containing this patch. No additional mitigation is required beyond applying the official fix.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-843v-cg64-5wvw
Osv Schema Version
1.4.0
Aliases
["CVE-2026-98564"]

Threat ID: 6ad520af2cdf04f656993ab3

Added to database: 10/18/2026, 19:40:31 UTC

Last enriched: 10/18/2026, 20:49:24 UTC

Last updated: 10/18/2026, 22:28:12 UTC

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses