# CVE-2026-97434: dpaa2-switch: fix handling of NAPI on the remove path

> A use-after-free vulnerability in the Linux kernel dpaa2-switch driver allows local attackers to cause a denial of service or potentially execute code during device removal.

- **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:** 24 Sep 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-103610, BELL-CVE-2026-97434, DEBIAN-CVE-2026-97434, GHSA-pf43-5wcw-xwvc, UBUNTU-CVE-2026-97434

## What is CVE-2026-97434?

CVE-2026-97434 is an use after free vulnerability in Linux, published on 24 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:

dpaa2-switch: fix handling of NAPI on the remove path

All the NAPI instances for a DPSW device are attached to the first
switch port's net_device but shared by all ports. The NAPI instances get
disabled only once the last port goes down.

This causes an issue on the .remove() path where each port is
unregistered and freed one at a time, causing the NAPI instances to be
deleted even though they are not disabled.

In order to avoid this, split up the unregister_netdev() calls from the
free_netdev() so that we make sure all ports go down before we attempt
a deletion of NAPI instances. Also, make the netif_napi_del() explicit
as it is on the .probe() path.

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


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

Apply the vendor's patch.

## Is CVE-2026-97434 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97434 is an use after free vulnerability in Linux, published on 24 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-97434 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-97434/ (Markdown: https://insights.sbomify.com/CVE-2026-97434/index.md)
```

## Sources

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

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