Skip to content
VulniPulse
UnratedRed Hat Linux

Advisory [CVE-2026-64143] Do not enable the charging limit even when forced

This security Red Hat Linux advisory covers CVE-2026-64143.

CVE-2026-64143 Published Jul 19, 2026Updated by vendor Jul 19, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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. This vulnerability allows a local user to potentially cause permanent damage to the battery on certain older Uniwill laptop models.

The issue arises when the battery charging limit feature is enabled through a 'force' module parameter, as some devices do not properly implement this interface. Preventing the use of this feature, even when forced, avoids irreversible hardware damage.

Red Hat severity: not rated. Weakness: CWE-920.

Red Hat lists Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 6; Red Hat Enterprise Linux 7; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9 as not affected.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · medium-confidence parse· fetched 7 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · medium-confidence parse· fetched 7 days ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · medium-confidence parse· fetched 7 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.