# CVE-2026-89970: nvmet-auth: Synchronize timeout work during SQ teardown

> A race condition in Linux kernel NVMe target authentication allows use-after-free during queue teardown, potentially leading to code execution or denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101460, BELL-CVE-2026-89970, DEBIAN-CVE-2026-89970, GHSA-p375-rp8x-7v2g, UBUNTU-CVE-2026-89970

## What is CVE-2026-89970?

CVE-2026-89970 is a critical vulnerability in Linux, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

nvmet-auth: Synchronize timeout work during SQ teardown

nvmet_auth_sq_free() cancels auth_expired_work with
cancel_delayed_work(). If the work has already started, cancellation does
not wait for the callback. Transport teardown can consequently free or
reuse the queue containing struct nvmet_sq while
nvmet_auth_expired_work() still accesses that SQ.

Add a teardown-specific helper that synchronously drains the delayed work
before freeing authentication state, and use it from nvmet_sq_destroy().
Keep the non-synchronous helper for in-band authentication state cleanup,
where the SQ owner remains alive.

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


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

Apply the vendor's patch.

## Is CVE-2026-89970 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89970 is a critical vulnerability in Linux, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89970 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-89970/ (Markdown: https://insights.sbomify.com/CVE-2026-89970/index.md)
```

## Sources

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

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