# CVE-2025-37933: octeon_ep: Fix host hang issue during device reboot

> A use-after-free bug in the octeon_ep driver causes a host hang during device reboot, requiring a kernel patch to prevent denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 May 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-37933, DEBIAN-CVE-2025-37933, GHSA-q8rr-8fcc-gc56, ROOT-OS-UBUNTU-2404-CVE-2025-37933, UBUNTU-CVE-2025-37933

## What is CVE-2025-37933?

CVE-2025-37933 is a medium-severity use after free vulnerability in Linux kernel, published on 20 May 2025. 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:

octeon_ep: Fix host hang issue during device reboot

When the host loses heartbeat messages from the device,
the driver calls the device-specific ndo_stop function,
which frees the resources. If the driver is unloaded in
this scenario, it calls ndo_stop again, attempting to free
resources that have already been freed, leading to a host
hang issue. To resolve this, dev_close should be called
instead of the device-specific stop function.dev_close
internally calls ndo_stop to stop the network interface
and performs additional cleanup tasks. During the driver
unload process, if the device is already down, ndo_stop
is not called.

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2025-37933?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-37933?

Apply the vendor's patch.

## Is CVE-2025-37933 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-37933 and fix it if it is affected.

What it is: CVE-2025-37933 is a medium-severity use after free vulnerability in Linux kernel, published on 20 May 2025. 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-2025-37933 in the wild and no public exploit code.

Affected product: Linux kernel. 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-2025-37933/ (Markdown: https://insights.sbomify.com/CVE-2025-37933/index.md)
```

## Sources

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

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