# CVE-2026-99197: net: mv643xx: move setting of netops to fix crash


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-99197, GHSA-xp2p-g3gh-w84x, UBUNTU-CVE-2026-99197

## What is CVE-2026-99197?

CVE-2026-99197 is a vulnerability in Linux, published on 28 Oct 2026. 

### Official description

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

net: mv643xx: move setting of netops to fix crash

mv643xx_eth_probe() connects the PHY before dev->netdev_ops is
assigned. phy_attach_direct() -> phy_link_topo_add_phy() reads
dev->netdev_ops through netdev_need_ops_lock() since the commit in
question, so probing crashes with a NULL pointer dereference when
CONFIG_NET_SHAPER is enabled.

Assign netdev_ops before the PHY attach, as was done for emac in commit
7c9f391ec89c ("net: emac: move setting of netops to fix crash").

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


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

Upgrade to a fixed version.

## Is CVE-2026-99197 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99197 is a vulnerability in Linux, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99197 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-99197/ (Markdown: https://insights.sbomify.com/CVE-2026-99197/index.md)
```

## Sources

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

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