# CVE-2026-93279: staging: octeon: add missing tasklet_kill in cvm_oct_tx_shutdown

> A use-after-free vulnerability in the Linux kernel Octeon driver allows local attackers to cause denial of service or potentially escalate privileges.

- **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-93279, DEBIAN-CVE-2026-93279, GHSA-j68w-r43c-3g43, UBUNTU-CVE-2026-93279

## What is CVE-2026-93279?

CVE-2026-93279 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 tasklet_kill in cvm_oct_tx_shutdown

The TX cleanup tasklet can be scheduled by the watchdog IRQ handler
to execute cvm_oct_tx_do_cleanup. There can be a pending tasklet in
the queue which might run after the cvm_oct_remove() frees net_device
structures, causing a use-after-free in cvm_oct_tx_do_cleanup() as it
iterates cvm_oct_device[] which is an array of netdevice pointers.
Add tasklet_kill() after free_irq() to ensure the tasklet is no longer
scheduled or running before teardown proceeds.

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


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

Apply the vendor's patch.

## Is CVE-2026-93279 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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