# CVE-2026-68152: amt: fix use-after-free in AMT delayed works

> A use-after-free vulnerability in the Linux kernel AMT module allows attackers to cause crashes or execute code via a race condition 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:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** AZL-94913, BELL-CVE-2026-68152, DEBIAN-CVE-2026-68152, GHSA-3v9r-4x9w-8c55, UBUNTU-CVE-2026-68152

## What is CVE-2026-68152?

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

amt: fix use-after-free in AMT delayed works

When an AMT device is removed, pending delayed works can still access
the freed amt_dev structure, which may result in kernel crashes or
memory corruption.

amt_dev_stop() cancels req_wq and discovery_wq with
cancel_delayed_work_sync(), but these works can be scheduled again
from event_wq after the cancellation. This allows delayed works to
access the freed amt_dev structure after the netdev has been released.

The following is a simple race scenario:

CPU0                         CPU1

amt_dev_stop()
cancel_delayed_work_sync()
                             amt_event_work()
                             mod_delayed_work(req_wq)
free netdev
                             req_wq accesses freed amt_dev

Use disable_delayed_work_sync() in amt_dev_stop() to prevent req_wq and
discovery_wq from being queued again and wait for running work items
to complete.

The delayed works are disabled after initialization in
amt_newlink() and enabled only when the device is successfully opened.
This keeps the delayed work lifecycle synchronized with the lifetime
of the AMT device.

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


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

Apply the vendor's patch.

## Is CVE-2026-68152 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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