CVE-2026-64143

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-19. 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:

platform/x86: uniwill-laptop: Do not enable the charging limit even when forced

It seems that on some older models (~2020) the battery charging limit can permanently damage the battery. Prevent users from enabling this feature thru the "force" module parameter to avoid causing permanent hardware damage on such devices.

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
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (2)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

platform/x86: uniwill-laptop: Do not enable the charging limit even when forced - kernel/git/stable/linux.git - Linux kernel stable tree

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

platform/x86: uniwill-laptop: Do not enable the charging limit even when forced - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26cbe119f99c86dcb4a0136d2bc73c0c716d80e4

Vendor Advisories for CVE-2026-64143(1)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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 (138 versions)7.0.12-1—

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 20× in last 7d / 69× 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.

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

Frequently asked(5)

What is CVE-2026-64143?
CVE-2026-64143 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: platform/x86: uniwill-laptop: Do not enable the charging limit even when forced It seems that on some older models (~2020) the battery charging limit can permanently damage the battery. Prevent users from enabling this feature thru…
When was CVE-2026-64143 disclosed?
CVE-2026-64143 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64143 actively exploited?
CVE-2026-64143 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64143?
CVE-2026-64143 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64143?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64143, 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-64143

Explore →

Is Your Infrastructure Affected by CVE-2026-64143?

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

Start Free Scan →Browse All CVEs