CVE-2026-89462

Incorrect battery telemetry via ignored I2C read errors

Published Sep 11, 2026 · Updated Sep 11, 2026

Incorrect battery telemetry in the Linux max17040 driver causes bogus voltage or charge data to reach userspace after I2C failures. max17040_get_vcell() and max17040_get_soc() ignore regmap_read() errors, convert uninitialized values, and let polling overwrite cached charge state. Reachability requires max17040-compatible fuel-gauge hardware and an I2C read failure; consequences are limited to incorrect telemetry and spurious change events.

CVSS severityUnavailable
Unscored
EPSS probability0.17%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect battery telemetry in the Linux max17040 driver causes bogus voltage or charge data to reach userspace after I2C failures. max17040_get_vcell() and max17040_get_soc() ignore regmap_read() errors, convert uninitialized values, and let polling overwrite cached charge state. Reachability requires max17040-compatible fuel-gauge hardware and an I2C read failure; consequences are limited to incorrect telemetry and spurious change events.

The record

CVE
CVE-2026-89462
Published
Sep 11, 2026
Updated
Sep 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Sep 11, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2.6.31
  2. Affected versionversion=c6f4a42de60b981dd210de01cd3e575835e3158e <13fb0477da9b400071b9d518b24d6434c4965263
  3. Affected versionversion=c6f4a42de60b981dd210de01cd3e575835e3158e <2943a0edd4865ed744702ada647921c3981207f6
  4. Affected versionversion=c6f4a42de60b981dd210de01cd3e575835e3158e <659cc3d8d5ef246263873fce72c8cadeeed073cc
  5. Affected versionversion=c6f4a42de60b981dd210de01cd3e575835e3158e <c7aa4c3708cc0d8487336f8281665eaea87130f6

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=2.6.31; version=c6f4a42de60b981dd210de01cd3e575835e3158e <13fb0477da9b400071b9d518b24d6434c4965263; version=c6f4a42de60b981dd210de01cd3e575835e3158e <2943a0edd4865ed744702ada647921c3981207f6; version=c6f4a42de60b981dd210de01cd3e575835e3158e <659cc3d8d5ef246263873fce72c8cadeeed073cc; version=c6f4a42de60b981dd210de01cd3e575835e3158e <c7aa4c3708cc0d8487336f8281665eaea87130f6

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo