Out-of-bounds read via invalid current-limit index
Published Jan 11, 2025 · Updated Aug 5, 2026
Out-of-bounds access in Linux's gpio-charger driver allows local users to read adjacent kernel memory via a current-limit write. The driver's set_charge_current_limit path uses current_limit_map_size as an array index when the requested limit is below the smallest mapped value. Reachability requires a gpio-charger device whose lowest permitted current exceeds zero and local permission to write its current-limit sysfs attribute.
Summary
What happened
Out-of-bounds access in Linux's gpio-charger driver allows local users to read adjacent kernel memory via a current-limit write. The driver's set_charge_current_limit path uses current_limit_map_size as an array index when the requested limit is below the smallest mapped value. Reachability requires a gpio-charger device whose lowest permitted current exceeds zero and local permission to write its current-limit sysfs attribute.
The record
- CVE
- CVE-2024-57792
- Published
- Jan 11, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 11, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
- Affected versionversion=5.10
- Affected versionversion=be2919d8355e4651386ad2fb61ddb6efe4533b1b <13eb3cae1d8e23cce96c095abe34da8028c09ac5
- Affected versionversion=be2919d8355e4651386ad2fb61ddb6efe4533b1b <6abbbd8286b6f944eecf3c74444c138590135211
- Affected versionversion=be2919d8355e4651386ad2fb61ddb6efe4533b1b <afc6e39e824ad0e44b2af50a97885caec8d213d1
- Affected versionversion=be2919d8355e4651386ad2fb61ddb6efe4533b1b <b29c7783ac1fe36d639c089cf471ac7a46df05f0
- Affected versionversion=be2919d8355e4651386ad2fb61ddb6efe4533b1b <c3703d9340ca2820e1ac63256f4b423ea8559831
- Affected versionversion=be2919d8355e4651386ad2fb61ddb6efe4533b1b <f6279a98db132da0cfff18712a1b06478c32007f
What conditions does exploitation require?
What is affected?
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.
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