CVE-2026-53308

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-26. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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:

  • Driver leaks the memory on remove(), because the workqueue is not
destroyed.
  • 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
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

June 26, 2026

Last Modified

July 6, 2026

Advisory Details (2)

Auto-updated Jul 9, 2026
No patch confirmed yet.
generic

power: supply: max77705: Free allocated workqueue and fix removal order - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b98e4e57e34d099a8f846fa54749654082975ea0
generic

power: supply: max77705: Free allocated workqueue and fix removal order - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1e668baadefb16e81269dbfebf3ffc2672e3a3bb

Vendor Advisories for CVE-2026-53308(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 9× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 182 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 07:08 UTCEG score recompute
  3. 2026-09-18 07:08 UTCVendor advisory
  4. 2026-09-18 07:08 UTCGHSA enrichment
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-14 00:57 UTCEG score recompute
  8. 2026-09-14 00:57 UTCVendor advisory
  9. 2026-09-14 00:57 UTCGHSA enrichment
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-12 15:30 UTCEG score recompute
  12. 2026-09-12 15:30 UTCVendor advisory
  13. 2026-09-12 15:30 UTCGHSA enrichment
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-10 09:35 UTCEPSS rescore
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-07 16:01 UTCEPSS rescore
  18. 2026-09-06 14:56 UTCEG score recompute
  19. 2026-09-06 14:56 UTCVendor advisory
  20. 2026-09-06 14:56 UTCGHSA enrichment
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-04 05:06 UTCEPSS rescore
  23. 2026-09-02 14:12 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-08-30 19:17 UTCEPSS rescore
Show 75 more
  1. 2026-08-30 19:15 UTCEG score recompute
  2. 2026-08-30 19:15 UTCVendor advisory
  3. 2026-08-30 19:15 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:41 UTCEPSS rescore
  6. 2026-08-27 22:54 UTCEG score recompute
  7. 2026-08-27 22:54 UTCVendor advisory
  8. 2026-08-27 22:54 UTCGHSA enrichment
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-24 12:45 UTCEG score recompute
  13. 2026-08-24 12:45 UTCVendor advisory
  14. 2026-08-24 12:45 UTCGHSA enrichment
  15. 2026-08-23 09:30 UTCEG score recompute
  16. 2026-08-23 09:30 UTCVendor advisory
  17. 2026-08-23 09:30 UTCGHSA enrichment
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-22 09:21 UTCEG score recompute
  20. 2026-08-22 09:21 UTCVendor advisory
  21. 2026-08-22 09:21 UTCGHSA enrichment
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-21 06:43 UTCEG score recompute
  24. 2026-08-21 06:43 UTCVendor advisory
  25. 2026-08-21 06:43 UTCGHSA enrichment
  26. 2026-08-20 22:55 UTCEPSS rescore
  27. 2026-08-20 06:34 UTCEG score recompute
  28. 2026-08-20 06:34 UTCVendor advisory
  29. 2026-08-20 06:34 UTCGHSA enrichment
  30. 2026-08-19 17:04 UTCEPSS rescore
  31. 2026-08-18 23:36 UTCEG score recompute
  32. 2026-08-18 23:36 UTCVendor advisory
  33. 2026-08-18 23:36 UTCGHSA enrichment
  34. 2026-08-18 13:48 UTCEPSS rescore
  35. 2026-08-17 13:47 UTCEPSS rescore
  36. 2026-08-17 04:29 UTCEG score recompute
  37. 2026-08-17 04:29 UTCVendor advisory
  38. 2026-08-17 04:29 UTCGHSA enrichment
  39. 2026-08-16 14:56 UTCEPSS rescore
  40. 2026-08-16 04:20 UTCEG score recompute
  41. 2026-08-16 04:20 UTCVendor advisory
  42. 2026-08-16 04:20 UTCGHSA enrichment
  43. 2026-08-16 02:14 UTCEPSS rescore
  44. 2026-08-15 04:11 UTCEG score recompute
  45. 2026-08-15 04:11 UTCVendor advisory
  46. 2026-08-15 04:11 UTCGHSA enrichment
  47. 2026-08-15 01:30 UTCEPSS rescore
  48. 2026-08-14 04:01 UTCEG score recompute
  49. 2026-08-14 04:01 UTCVendor advisory
  50. 2026-08-14 04:01 UTCGHSA enrichment
  51. 2026-08-13 22:00 UTCEPSS rescore
  52. 2026-08-13 03:52 UTCVendor advisory
  53. 2026-08-13 03:52 UTCGHSA enrichment
  54. 2026-08-12 03:44 UTCEG score recompute
  55. 2026-08-12 03:44 UTCVendor advisory
  56. 2026-08-12 03:44 UTCGHSA enrichment
  57. 2026-08-11 03:35 UTCVendor advisory
  58. 2026-08-11 03:35 UTCGHSA enrichment
  59. 2026-08-10 03:26 UTCEG score recompute
  60. 2026-08-10 03:26 UTCVendor advisory
  61. 2026-08-10 03:26 UTCGHSA enrichment
  62. 2026-08-09 13:46 UTCEPSS rescore
  63. 2026-08-09 03:18 UTCEG score recompute
  64. 2026-08-09 03:18 UTCVendor advisory
  65. 2026-08-09 03:18 UTCGHSA enrichment
  66. 2026-08-08 16:37 UTCEPSS rescore
  67. 2026-08-08 03:09 UTCEG score recompute
  68. 2026-08-08 03:09 UTCVendor advisory
  69. 2026-08-08 03:09 UTCGHSA enrichment
  70. 2026-08-07 03:00 UTCEG score recompute
  71. 2026-08-07 03:00 UTCVendor advisory
  72. 2026-08-07 03:00 UTCGHSA enrichment
  73. 2026-08-06 13:47 UTCEPSS rescore
  74. 2026-08-06 02:51 UTCEG score recompute
  75. 2026-08-06 02:51 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-53308?
CVE-2026-53308 is a medium vulnerability published on June 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.…
When was CVE-2026-53308 disclosed?
CVE-2026-53308 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53308 actively exploited?
CVE-2026-53308 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.0% of all scored CVEs.
What is the CVSS score of CVE-2026-53308?
CVE-2026-53308 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53308?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53308, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53308

Explore →

Is Your Infrastructure Affected by CVE-2026-53308?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.