Incorrect chip configuration via unchecked PMIC array index
Published Jun 8, 2026 · Updated Jun 8, 2026
Out-of-bounds read in the Linux Kernel qcom-lpg LED driver causes incorrect chip configuration when a PMIC register holds an invalid value. In lpg_pwm_get_state, FIELD_GET extracts a three-bit selector and uses it directly to index the five-entry lpg_clk_rates_hi_res array. The condition requires invalid hardware state that software attackers cannot invoke or influence, so the consequence is limited to random data being applied as chip settings.
Summary
What happened
Out-of-bounds read in the Linux Kernel qcom-lpg LED driver causes incorrect chip configuration when a PMIC register holds an invalid value. In lpg_pwm_get_state, FIELD_GET extracts a three-bit selector and uses it directly to index the five-entry lpg_clk_rates_hi_res array. The condition requires invalid hardware state that software attackers cannot invoke or influence, so the consequence is limited to random data being applied as chip settings.
The record
- CVE
- CVE-2026-46286
- Published
- Jun 8, 2026
- Updated
- Jun 8, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 8, 2026CVE publishedPublication date reported by the CVE source.
- Jun 8, 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=0 <6.12.86
- Affected versionversion=0 <6.18.27
- Affected versionversion=0 <6.6.140
- Affected versionversion=0 <7.0.4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <28a2e047d03721e0517c67ee726eaa6621c30e5f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <36ce3094dc50598f38fd961b46688cd533940efc
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <438e357b3cc6cd6900df271e4bc567bfe1142281
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d45963a93c1495e9f1338fde91d0ebba8fd22474
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f67a24e75d3251ba42538738120b6b659c0dca7d
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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