# CVE-2026-93278: staging: octeon: add missing napi_disable in cvm_oct_rx_shutdown

> A use-after-free vulnerability in the Linux kernel Octeon driver allows local attackers to cause a system crash by triggering a race condition 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:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93278, DEBIAN-CVE-2026-93278, GHSA-7ppg-qghw-hg2g, UBUNTU-CVE-2026-93278

## What is CVE-2026-93278?

CVE-2026-93278 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:

staging: octeon: add missing napi_disable in cvm_oct_rx_shutdown

cvm_oct_rx_shutdown calls free_irq and netif_napi_del without
disabling the napi instance first. As the free_irq only waits
for completion of hard interrupt handlers, the napi poll
function could still be active. If cvm_oct_remove proceeds to
free the plat structure (which holds the NAPI instances), the
active poll function will access freed memory, resulting in a
use-after-free crash.

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


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

Apply the vendor's patch.

## Is CVE-2026-93278 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93278 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-93278 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-93278/ (Markdown: https://insights.sbomify.com/CVE-2026-93278/index.md)
```

## Sources

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

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