Answer in brief
CVE-2026-89970 records a Unknown severity vulnerability in nvmet-auth: Synchronize timeout work during SQ teardown. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1a70200f404ae210b4f0334e3936e84f8edb6bc8 <664022fa1c93f4eba09ef5ee02411b9709dd7a93 || >=1a70200f404ae210b4f0334e3936e84f8edb6bc8 <c3c126a6142a1335bc8c34a5607c39cf01daf295 || >=1a70200f404ae210b4f0334e3936e84f8edb6bc8 <c17c87bde6d6f5252a6a6f0a94b2430164aa28d5 || >=1a70200f404ae210b4f0334e3936e84f8edb6bc8 <7555ddd60af72df2862dd8f9b730a9848577edda || >=1a70200f404ae210b4f0334e3936e84f8edb6bc8 <eb4f9127a2b8a152743f1ee597627e2f69cb54fe || >=1a70200f404ae210b4f0334e3936e84f8edb6bc8 <eaa948c0e19b1bb2d93262207bca0c3d19cc3406 | 664022fa1c93f4eba09ef5ee02411b9709dd7a93, c3c126a6142a1335bc8c34a5607c39cf01daf295, c17c87bde6d6f5252a6a6f0a94b2430164aa28d5, 7555ddd60af72df2862dd8f9b730a9848577edda, eb4f9127a2b8a152743f1ee597627e2f69cb54fe, eaa948c0e19b1bb2d93262207bca0c3d19cc3406 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.