VulnerabilityPublished 28 Oct 2026

CVE-2026-99197: Linux kernel · net: mv643xx: move setting of netops to fix crash

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to bfb1ca89e9f6efa26c8a4a5b9de46541a222abc9 or a3eef3d2cca032d8768b5eb07aab0f46b79bfd8a when convenient.

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in bfb1ca89e9f6efa26c8a4a5b9de46541a222abc9, a3eef3d2cca032d8768b5eb07aab0f46b79bfd8a

Exploitation evidence

Disclosed: evidence found.
CVE published 28 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.

What to do

Upgrade Linux kernel to bfb1ca89e9f6efa26c8a4a5b9de46541a222abc9 or a3eef3d2cca032d8768b5eb07aab0f46b79bfd8a.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ ded86da4bbb78cad74cecc368fee3ae3a296e2ca, < bfb1ca89e9f6efa26c8a4a5b9de46541a222abc9	Fixed in bfb1ca89e9f6efa26c8a4a5b9de46541a222abc9
LinuxLinux	Affected ≥ ded86da4bbb78cad74cecc368fee3ae3a296e2ca, < a3eef3d2cca032d8768b5eb07aab0f46b79bfd8a	Fixed in a3eef3d2cca032d8768b5eb07aab0f46b79bfd8a
LinuxLinux	Affected =7.2	Fixed in–

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").

References

Community reviews

Loading reviews…