# CVE-2026-98909: net: cpsw_new: unregister devlink on port registration failure


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-110671, BELL-CVE-2026-98909, DEBIAN-CVE-2026-98909, GHSA-7h76-g88g-x9j7, UBUNTU-CVE-2026-98909

## What is CVE-2026-98909?

CVE-2026-98909 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

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

net: cpsw_new: unregister devlink on port registration failure

cpsw_probe() registers devlink before registering the CPSW ports.

If cpsw_register_ports() fails, the error path only unregisters the
notifiers and then releases the lower level resources. It does not undo
the successful cpsw_register_devlink() call, leaving the devlink instance
and its parameters registered after probe has failed.

Add a devlink cleanup label for the path where devlink registration has
already succeeded, and use it when port registration fails.

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


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

Upgrade to a fixed version.

## Is CVE-2026-98909 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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