Kernel stack disclosure via uninitialized KMX61 buffer
Published Jan 19, 2025 · Updated May 11, 2026
Information disclosure in the KMX61 IIO driver in the Linux kernel allows local users to read uninitialized kernel stack data via buffered sensor output. The triggered-buffer handler fills only active-channel elements of its local array, then copies the entire array to user space without initializing the remaining elements. Access requires a system using the KMX61 sensor driver and a triggered IIO buffer; disclosed bytes are limited to residual kernel stack contents.
Summary
What happened
Information disclosure in the KMX61 IIO driver in the Linux kernel allows local users to read uninitialized kernel stack data via buffered sensor output. The triggered-buffer handler fills only active-channel elements of its local array, then copies the entire array to user space without initializing the remaining elements. Access requires a system using the KMX61 sensor driver and a triggered IIO buffer; disclosed bytes are limited to residual kernel stack contents.
The record
- CVE
- CVE-2024-57908
- Published
- Jan 19, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-908, T1005
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 19, 2025CVE publishedPublication date reported by the CVE source.
- May 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.
- Affected versionversion=4.0
- Affected versionversion=c3a23ecc0901f624b681bbfbc4829766c5aa3070 <0871eb8d700b33dd7fa86c80630d62ddaef58c2c
- Affected versionversion=c3a23ecc0901f624b681bbfbc4829766c5aa3070 <565814cbbaa674d2901428796801de49a611e59d
- Affected versionversion=c3a23ecc0901f624b681bbfbc4829766c5aa3070 <6985ba4467e4b15b809043fa7740d1fb23a1897b
- Affected versionversion=c3a23ecc0901f624b681bbfbc4829766c5aa3070 <6ae053113f6a226a2303caa4936a4c37f3bfff7b
- Affected versionversion=c3a23ecc0901f624b681bbfbc4829766c5aa3070 <a07f698084412a3ef5e950fcac1d6b0f53289efd
- Affected versionversion=c3a23ecc0901f624b681bbfbc4829766c5aa3070 <a386d9d2dc6635f2ec210b8199cfb3acf4d31305
- Affected versionversion=c3a23ecc0901f624b681bbfbc4829766c5aa3070 <cde312e257b59ecaa0fad3af9ec7e2370bb24639
What conditions does exploitation require?
What is affected?
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.
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