# CVE-2026-80711: power: supply: max17040: handle missing status supplier

> Local attackers can read uninitialized memory from battery status due to missing error handling in the MAX17040 driver.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** BELL-CVE-2026-80711, DEBIAN-CVE-2026-80711, GHSA-65qq-wp3h-275r, UBUNTU-CVE-2026-80711

## What is CVE-2026-80711?

CVE-2026-80711 is a vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-80711?


## How do I fix CVE-2026-80711?

Apply the vendor's patch.

## Is CVE-2026-80711 being exploited?

There is no known exploitation of CVE-2026-80711 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80711 and fix it if it is affected.

What it is: CVE-2026-80711 is a vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80711 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80711/ (Markdown: https://insights.sbomify.com/CVE-2026-80711/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80711
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80711
- OSV: https://osv.dev/vulnerability/CVE-2026-80711

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80711/
Summaries are generated and may contain mistakes; the official description above is the record.