In the Linux kernel, the following vulnerability has been resolved: power: supply: max77705: Free allocated workqueue and fix removal order Use devm… (CVE-2026-53308)
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.
AI Analysis
Technical Summary
The Linux kernel max77705 power supply driver had two related bugs: it leaked memory on removal because the workqueue was not destroyed, and it used a devm interface to register interrupt handlers after allocating the workqueue, causing a race condition during removal. Specifically, the interrupt handler could schedule work on a workqueue that had already been destroyed but before the interrupt was freed, leading to use-after-free memory access. The fix involved switching to a non-legacy workqueue API without legacy flags and using the devm interface to properly manage the lifecycle and destruction order of the workqueue and interrupt handlers.
Potential Impact
This vulnerability can cause a use-after-free condition resulting in potential system instability or denial of service due to the kernel accessing freed memory. There is no indication of confidentiality or integrity impact. The CVSS vector indicates local attack vector with low complexity and low privileges required, no user interaction, and an impact limited to availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description indicates the issue has been resolved in the Linux kernel by changing the driver code to use the devm interface and a non-legacy workqueue API. Users should apply the official Linux kernel updates containing this fix once available.
In the Linux kernel, the following vulnerability has been resolved: power: supply: max77705: Free allocated workqueue and fix removal order Use devm… (CVE-2026-53308)
Description
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.
CVSS v3.1
Score 5.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel max77705 power supply driver had two related bugs: it leaked memory on removal because the workqueue was not destroyed, and it used a devm interface to register interrupt handlers after allocating the workqueue, causing a race condition during removal. Specifically, the interrupt handler could schedule work on a workqueue that had already been destroyed but before the interrupt was freed, leading to use-after-free memory access. The fix involved switching to a non-legacy workqueue API without legacy flags and using the devm interface to properly manage the lifecycle and destruction order of the workqueue and interrupt handlers.
Potential Impact
This vulnerability can cause a use-after-free condition resulting in potential system instability or denial of service due to the kernel accessing freed memory. There is no indication of confidentiality or integrity impact. The CVSS vector indicates local attack vector with low complexity and low privileges required, no user interaction, and an impact limited to availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description indicates the issue has been resolved in the Linux kernel by changing the driver code to use the devm interface and a non-legacy workqueue API. Users should apply the official Linux kernel updates containing this fix once available.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2vjf-7vmh-8jpp
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53308"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a4c33fe27e9c797195f4578
Added to database: 07/06/2026, 23:02:22 UTC
Last enriched: 07/06/2026, 23:09:49 UTC
Last updated: 07/31/2026, 19:24:50 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.