# CVE-2026-97973: net: macb: destroy the phylink instance on the probe error path

> A memory leak in the Linux kernel macb driver probe error path can lead to resource exhaustion and denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-104835, BELL-CVE-2026-97973, DEBIAN-CVE-2026-97973, GHSA-rvwv-vg3x-5m3f, UBUNTU-CVE-2026-97973

## What is CVE-2026-97973?

CVE-2026-97973 is a memory corruption vulnerability in Linux, published on 25 Sep 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: macb: destroy the phylink instance on the probe error path

macb_mii_init() creates a phylink instance on both of its success paths,
but the probe unwind frees the netdev without destroying it, so a failing
macb_alloc_tieoff() or register_netdev() leaks the instance.

Destroy it at err_out_unregister_mdio, which is only reachable once
macb_mii_init() has succeeded, so bp->phylink is valid there.

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


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

Apply the vendor's patch.

## Is CVE-2026-97973 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97973 is a memory corruption vulnerability in Linux, published on 25 Sep 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-97973 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-97973/ (Markdown: https://insights.sbomify.com/CVE-2026-97973/index.md)
```

## Sources

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

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