VulnerabilityPublished 18 Oct 2026

CVE-2026-98564: Linux kernel · net: dsa: mt7530: leave the MDIO IRQ mappings to regmap-irq

Source GCVE Database

Authoritative record:CVE-2026-98564· Medium

Not known to be exploited · fixed in f306e465b5a2091cd3fe3dd0feb10cfc94cfb2f8 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in f306e465b5a2091cd3fe3dd0feb10cfc94cfb2f8, 2357c682f6eaf639dec88c68b3c0c93a3b802635, 0d80ba0a204c6a16bd7778b50de578dff107c0fe

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-843v-cg64-5wvw

What to do

Upgrade Linux kernel to f306e465b5a2091cd3fe3dd0feb10cfc94cfb2f8, 2357c682f6eaf639dec88c68b3c0c93a3b802635 or 0d80ba0a204c6a16bd7778b50de578dff107c0fe.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 254f6b272e3b67bf31c42ee9da62a449d74d1478, < f306e465b5a2091cd3fe3dd0feb10cfc94cfb2f8	Fixed in f306e465b5a2091cd3fe3dd0feb10cfc94cfb2f8
LinuxLinux	Affected ≥ 254f6b272e3b67bf31c42ee9da62a449d74d1478, < 2357c682f6eaf639dec88c68b3c0c93a3b802635	Fixed in 2357c682f6eaf639dec88c68b3c0c93a3b802635
LinuxLinux	Affected ≥ 254f6b272e3b67bf31c42ee9da62a449d74d1478, < 0d80ba0a204c6a16bd7778b50de578dff107c0fe	Fixed in 0d80ba0a204c6a16bd7778b50de578dff107c0fe
LinuxLinux	Affected =6.15	Fixed in–

AI-suggested

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.

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.

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.

References

Community reviews

Loading reviews…