Answer in brief
CVE-2026-98015 records a Unknown severity vulnerability in net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put. 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 | >=10caabdaad5ace85577a453da97d1f8d3b944427 <304ea40ef4561671503c36e47da44a0a31b71e36 || >=10caabdaad5ace85577a453da97d1f8d3b944427 <e393789e92310d7c66f57c876101779c90816a12 || >=10caabdaad5ace85577a453da97d1f8d3b944427 <18b2969073879b9cce24e1a78b118bdad54518d1 || >=10caabdaad5ace85577a453da97d1f8d3b944427 <7ee07f601f8f507c9faf25c68a49396ab8950596 | 304ea40ef4561671503c36e47da44a0a31b71e36, e393789e92310d7c66f57c876101779c90816a12, 18b2969073879b9cce24e1a78b118bdad54518d1, 7ee07f601f8f507c9faf25c68a49396ab8950596 |
| Linux/Linuxgeneric | 5.3 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put In mlx5_eswitch_termtbl_put(), the zero-ref cleanup check reads tt->ref_count after termtbl_mutex has been released. Two concurrent callers on the same mlx5_termtbl_handle race: one decrements ref_count to zero, removes the hash entry, and calls kfree(tt) while the other has already dropped the mutex and is about to evaluate if (!tt->ref_count), producing a use-after-free. Fix this by capturing the result of the decrement into a stack-local last variable before dropping the mutex. The cleanup decision is now made entirely under termtbl_mutex, and tt is not touched after kfree.
Quoted source text, attributed separately from HOL analysis.