CVE-2023-53166

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2025-09-15. NVD baseline CVSS 4.7; sources differ by 0.0.

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

power: supply: bq25890: Fix external_power_changed race

bq25890_charger_external_power_changed() dereferences bq->charger, which gets sets in bq25890_power_supply_init() like this:

bq->charger = devm_power_supply_register(bq->dev, &bq->desc, &psy_cfg);

As soon as devm_power_supply_register() has called device_add() the external_power_changed callback can get called. So there is a window where bq25890_charger_external_power_changed() may get called while bq->charger has not been set yet leading to a NULL pointer dereference.

This race hits during boot sometimes on a Lenovo Yoga Book 1 yb1-x90f when the cht_wcove_pwrsrc (extcon) power_supply is done with detecting the connected charger-type which happens to exactly hit the small window:

BUG: kernel NULL pointer dereference, address: 0000000000000018 RIP: 0010:__power_supply_is_supplied_by+0xb/0xb0 Call Trace: __power_supply_get_supplier_property+0x19/0x50 class_for_each_device+0xb1/0xe0 power_supply_get_property_from_supplier+0x2e/0x50 bq25890_charger_external_power_changed+0x38/0x1b0 [bq25890_charger] __power_supply_changed_work+0x30/0x40 class_for_each_device+0xb1/0xe0 power_supply_changed_work+0x5f/0xe0

Fixing this is easy. The external_power_changed callback gets passed the power_supply which will eventually get stored in bq->charger, so bq25890_charger_external_power_changed() can simply directly use the passed in psy argument which is always valid.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
26(Track)
EG Risk 26/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
Severity47% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

September 15, 2025

Last Modified

November 24, 2025

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.31osv

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.27-16.1.37-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.3.7-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.3.7-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 26× 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 127 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2023-53166?
CVE-2023-53166 is a medium vulnerability published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: power: supply: bq25890: Fix externalpowerchanged race bq25890chargerexternalpowerchanged() dereferences bq->charger, which gets sets in bq25890powersupply_init() like this: bq->charger = devmpowersupplyregister(bq->dev, &bq->desc,…
When was CVE-2023-53166 disclosed?
CVE-2023-53166 was first published in the National Vulnerability Database on September 15, 2025, with the most recent update on November 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-53166 actively exploited?
CVE-2023-53166 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 98.6% of all scored CVEs.
What is the CVSS score of CVE-2023-53166?
CVE-2023-53166 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2023-53166?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53166, 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-2023-53166

Explore →

Is Your Infrastructure Affected by CVE-2023-53166?

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