# CVE-2026-74725: enic: fix tx_hang_reset use-after-free on device removal

> A use-after-free in the enic driver allows attackers to cause denial of service or execute code during device removal.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 22 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** AZL-97305, BELL-CVE-2026-74725, DEBIAN-CVE-2026-74725, GHSA-r6pf-7wx9-37hw, UBUNTU-CVE-2026-74725

## What is CVE-2026-74725?

CVE-2026-74725 is a high-severity use after free vulnerability in Linux, published on 22 Aug 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:

enic: fix tx_hang_reset use-after-free on device removal

enic_remove() cancels the reset and change_mtu_work items but does not
cancel tx_hang_reset. A TX timeout that fires while the device is being
removed can schedule enic_tx_hang_reset() so that it runs after
free_netdev(), resulting in a use-after-free.

cancel_work_sync() alone is not sufficient here: the still-live watchdog
and notify paths can re-schedule these work items in the window between
the cancel and unregister_netdev(). Use disable_work_sync(), which
cancels the work and blocks any subsequent schedule_work() from
requeuing it, and apply it to the reset and change_mtu_work items as
well so the same requeue race is closed for all teardown work.

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


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

Apply the vendor's patch.

## Is CVE-2026-74725 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74725 is a high-severity use after free vulnerability in Linux, published on 22 Aug 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-74725 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-74725/ (Markdown: https://insights.sbomify.com/CVE-2026-74725/index.md)
```

## Sources

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

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