PatchSiren cyber security CVE debrief
CVE-2026-89462 Linux CVE debrief
A vulnerability in the Linux kernel's power supply driver for max17040 has been addressed. The max17040_get_vcell() and max17040_get_soc() functions ignored errors returned by regmap_read(). When an I2C transfer fails, the uninitialized register value is converted and reported to userspace as a valid voltage or state of charge. The polling worker can also replace the cached state of charge with the bogus value and emit a spurious change event. Propagate read errors through the power supply get_property callback and keep the last valid cached state of charge when polling fails.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-11
- Original CVE updated
- 2026-09-11
- Advisory published
- 2026-09-11
- Advisory updated
- 2026-09-11
Who should care
Linux kernel maintainers, Linux distribution maintainers, and users of Linux-based systems relying on max17040 power supply functionality should assess exposure and verify the fix.
Why it matters
A vulnerability in the Linux kernel's power supply driver for max17040 could lead to incorrect state of charge values being reported and spurious change events being emitted. Defenders should assess exposure and verify the fix.
- Defenders should verify the fix in Linux kernel deployments, especially in environments relying on max17040 power supply functionality.
- The bogus state of charge values could lead to incorrect monitoring and alerting.
- The spurious change events could cause unnecessary system reactions.
Technical summary
The max17040_get_vcell() and max17040_get_soc() functions in the Linux kernel's power supply driver ignored errors returned by regmap_read(). This could lead to bogus state of charge values being reported to userspace and spurious change events being emitted. The fix propagates read errors through the power supply get_property callback and keeps the last valid cached state of charge when polling fails.
Defensive priority
Linux kernel maintainers and users should assess exposure and verify the fix, especially in deployments relying on max17040 power supply functionality.
Recommended defensive actions
- Review and apply the patches provided in the Linux kernel Git repository to address the vulnerability.
- Verify the fix in the Linux kernel deployments, especially in environments relying on max17040 power supply functionality.
- Monitor for potential spurious change events caused by the bogus state of charge values.
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
Evidence notes
The CVE record and NVD entry provide details on the vulnerability. Four source references from the Linux kernel Git repository are available, detailing the patches applied to address the issue. The fix involves propagating read errors through the power supply get_property callback and keeping the last valid cached state of charge when polling fails. Linux kernel maintainers, Linux distribution maintainers, and users of Linux-based systems relying on max17040 power supply functionality should assess exposure and verify the fix. The bog
Sources and references
Verified primary and authoritative sources
-
CVE-2026-89462 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-89462
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-89462 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-89462
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/13fb0477da9b400071b9d518b24d6434c4965263
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/2943a0edd4865ed744702ada647921c3981207f6
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/659cc3d8d5ef246263873fce72c8cadeeed073cc
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/c7aa4c3708cc0d8487336f8281665eaea87130f6
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.