power: supply: max17040: handle missing status supplier
Summary
| CVE | CVE-2026-80711 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-28 08:16:56 UTC |
| Updated | 2026-08-28 08:16:56 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
power: supply: max17040: handle missing status supplier
MAX17040 does not report charger state itself, so the driver forwards
POWER_SUPPLY_PROP_STATUS to a supplier power supply. If no supplier is
registered, power_supply_get_property_from_supplier() returns -ENODEV and
leaves the output value untouched.
max17040_get_property() currently ignores that error and returns success,
so userspace can read an uninitialized status value from the battery power
supply. This happens on systems that use the fuel gauge without a charger
supplier relationship in firmware.
Return POWER_SUPPLY_STATUS_UNKNOWN when no supplier provides STATUS, and
propagate other supplier lookup errors. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected f4b782af61ae7bbf93008d5809b0e3a8ac2bb88e 91ac995a6f4ddf4f92b231b080544abf23a9b871 git |
Not specified |
| CNA |
Linux |
Linux |
affected f4b782af61ae7bbf93008d5809b0e3a8ac2bb88e b039f13e095d28a64ca6b21d0ee5440d8b048f37 git |
Not specified |
| CNA |
Linux |
Linux |
affected f4b782af61ae7bbf93008d5809b0e3a8ac2bb88e ee2ea0c452edc0930e7395b080dccd5a1cb965e1 git |
Not specified |
| CNA |
Linux |
Linux |
affected f4b782af61ae7bbf93008d5809b0e3a8ac2bb88e 725668c6b6aa3971fe850659102c250d0d676e18 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.7 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.7 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.103 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.44 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.8 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/b039f13e095d28a64ca6b21d0ee5440d8b048f37 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/ee2ea0c452edc0930e7395b080dccd5a1cb965e1 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/725668c6b6aa3971fe850659102c250d0d676e18 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/91ac995a6f4ddf4f92b231b080544abf23a9b871 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.