Answer in brief
CVE-2026-68152 records a Unknown severity vulnerability in amt: fix use-after-free in AMT delayed works. 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 | >=cbc21dc1cfe949e37b2a54c71511579f1899e8d4 <a46bfa01e01df0f6f6dc4b0be18db002d6d2dbd2 || >=cbc21dc1cfe949e37b2a54c71511579f1899e8d4 <1a644db2cf59f164cdf3c75995bab5aadc097528 || >=cbc21dc1cfe949e37b2a54c71511579f1899e8d4 <006340cf06881b6ff49767d8b6f3c4f7b892670c || >=cbc21dc1cfe949e37b2a54c71511579f1899e8d4 <ea20c44935d6142daecfa9b39d635033a7553e1b | a46bfa01e01df0f6f6dc4b0be18db002d6d2dbd2, 1a644db2cf59f164cdf3c75995bab5aadc097528, 006340cf06881b6ff49767d8b6f3c4f7b892670c, ea20c44935d6142daecfa9b39d635033a7553e1b |
| Linux/Linuxgeneric | 5.16 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68152 records a Unknown severity vulnerability in amt: fix use-after-free in AMT delayed works. 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 | >=cbc21dc1cfe949e37b2a54c71511579f1899e8d4 <a46bfa01e01df0f6f6dc4b0be18db002d6d2dbd2 || >=cbc21dc1cfe949e37b2a54c71511579f1899e8d4 <1a644db2cf59f164cdf3c75995bab5aadc097528 || >=cbc21dc1cfe949e37b2a54c71511579f1899e8d4 <006340cf06881b6ff49767d8b6f3c4f7b892670c || >=cbc21dc1cfe949e37b2a54c71511579f1899e8d4 <ea20c44935d6142daecfa9b39d635033a7553e1b | a46bfa01e01df0f6f6dc4b0be18db002d6d2dbd2, 1a644db2cf59f164cdf3c75995bab5aadc097528, 006340cf06881b6ff49767d8b6f3c4f7b892670c, ea20c44935d6142daecfa9b39d635033a7553e1b |
| Linux/Linuxgeneric | 5.16 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.