Answer in brief
CVE-2026-74725 records a Unknown severity vulnerability in enic: fix tx_hang_reset use-after-free on device removal. 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 | >=937317c7c1097aa878a5000e3aab616eb5c590c0 <8619865f34fb3b130b567855382a5c4aadd522b9 || >=937317c7c1097aa878a5000e3aab616eb5c590c0 <e506e704b74748ffd0e1c92a7453ca2a959f832b || >=937317c7c1097aa878a5000e3aab616eb5c590c0 <4f3464fc6c1f26afc504fd525c574f2bc14c9d42 || >=937317c7c1097aa878a5000e3aab616eb5c590c0 <ec680ea4ba1bca92a767fb7e7869758bfdd886e3 | 8619865f34fb3b130b567855382a5c4aadd522b9, e506e704b74748ffd0e1c92a7453ca2a959f832b, 4f3464fc6c1f26afc504fd525c574f2bc14c9d42, ec680ea4ba1bca92a767fb7e7869758bfdd886e3 |
| Linux/Linuxgeneric | 4.4 | Not reported |
Published upstream
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 22, 2026
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.
Quoted source text, attributed separately from HOL analysis.