Answer in brief
CVE-2026-53308 records a Medium severity (CVSS 5.5) vulnerability in power: supply: max77705: Free allocated workqueue and fix removal order. 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.
CVSS is 5.5. 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 | >=a6a494c8e3ce1fe84aac538b087a4cab868ed83f <4338663dfd21b9c6b012185e5c898769acb60692 || >=a6a494c8e3ce1fe84aac538b087a4cab868ed83f <b98e4e57e34d099a8f846fa54749654082975ea0 || >=a6a494c8e3ce1fe84aac538b087a4cab868ed83f <1e668baadefb16e81269dbfebf3ffc2672e3a3bb | 4338663dfd21b9c6b012185e5c898769acb60692, b98e4e57e34d099a8f846fa54749654082975ea0, 1e668baadefb16e81269dbfebf3ffc2672e3a3bb |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Jun 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 26, 2026
In the Linux kernel, the following vulnerability has been resolved: power: supply: max77705: Free allocated workqueue and fix removal order Use devm interface for allocating workqueue to fix two bugs at the same time: 1. Driver leaks the memory on remove(), because the workqueue is not destroyed. 2. Driver allocates workqueue and then registers interrupt handlers with devm interface. This means that probe error paths will not use a reversed order, but first destroy the workqueue and then, via devm release handlers, free the interrupt. The interrupt handler schedules work on this exact workqueue, thus if interrupt is hit in this short time window - after destroying workqueue, but before devm() frees the interrupt - the schedulled work will lead to use of freed memory. Change is not equivalent in the workqueue itself: use non-legacy API which does not set (__WQ_LEGACY | WQ_MEM_RECLAIM). The workqueue is used to update power supply (power_supply_changed()) status, thus there is no point to run it for memory reclaim. Note that dev_name() is not directly used in second argument to prevent possible unlikely parsing any "%" character in device name as format.
Quoted source text, attributed separately from HOL analysis.