# CVE-2026-98565: net: dsa: mt7530: fix NULL dereference on unbind of MT7531 and MT7621

> A local attacker with root privileges can cause a kernel crash by unbinding the MT7531 or MT7621 DSA driver due to a NULL pointer dereference.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-109307, BELL-CVE-2026-98565, DEBIAN-CVE-2026-98565, GHSA-4r34-63x3-rq2x, UBUNTU-CVE-2026-98565

## What is CVE-2026-98565?

CVE-2026-98565 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

net: dsa: mt7530: fix NULL dereference on unbind of MT7531 and MT7621

The core and io supplies are only requested for ID_MT7530: both the
devm_regulator_get() in probe and the regulator_enable() in
mt7530_setup() are guarded by the switch id, but mt7530_remove()
disables them unconditionally. On an MT7621 or an MT7531 both pointers
are still NULL from devm_kzalloc(), so rmmod or a sysfs unbind calls
regulator_disable() on NULL.

## Which versions are affected by CVE-2026-98565?


## How do I fix CVE-2026-98565?

Apply the vendor's patch.

## Is CVE-2026-98565 being exploited?

There is no known exploitation of CVE-2026-98565 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98565 and fix it if it is affected.

What it is: CVE-2026-98565 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98565 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98565/ (Markdown: https://insights.sbomify.com/CVE-2026-98565/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98565
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98565
- OSV: https://osv.dev/vulnerability/CVE-2026-98565

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98565/
Summaries are generated and may contain mistakes; the official description above is the record.