Kernel hang via zero-length FIFO pattern
Published May 20, 2025 · Updated May 11, 2026
Denial of service in the Linux st_lsm6dsx IMU driver allows local users to hang affected kernels through a nonempty device FIFO. st_lsm6dsx_read_tagged_fifo loops indefinitely when pattern_len is zero while the device FIFO still contains data, so the FIFO drain loop makes no progress. Reachability requires the affected IIO driver and compatible ST IMU hardware; the reported consequence is a kernel hang, not data access or modification.
Summary
What happened
Denial of service in the Linux st_lsm6dsx IMU driver allows local users to hang affected kernels through a nonempty device FIFO. st_lsm6dsx_read_tagged_fifo loops indefinitely when pattern_len is zero while the device FIFO still contains data, so the FIFO drain loop makes no progress. Reachability requires the affected IIO driver and compatible ST IMU hardware; the reported consequence is a kernel hang, not data access or modification.
The record
- CVE
- CVE-2025-37969
- Published
- May 20, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 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.20
- Affected versionversion=801a6e0af0c6cedca2e99155e343ad385a50f08e <16857370b3a30663515956b3bd27f3def6a2cf06
- Affected versionversion=801a6e0af0c6cedca2e99155e343ad385a50f08e <35b8c0a284983b71d92d082c54b7eb655ed4194f
- Affected versionversion=801a6e0af0c6cedca2e99155e343ad385a50f08e <4db7d923a8c298788181b796f71adf6ca499f966
- Affected versionversion=801a6e0af0c6cedca2e99155e343ad385a50f08e <76727a1d81afde77d21ea8feaeb12d34605be6f4
- Affected versionversion=801a6e0af0c6cedca2e99155e343ad385a50f08e <8114ef86e2058e2554111b793596f17bee23fa15
- Affected versionversion=801a6e0af0c6cedca2e99155e343ad385a50f08e <9ce662851380fe2018e36e15c0bdcb1ad177ed95
- Affected versionversion=801a6e0af0c6cedca2e99155e343ad385a50f08e <9ddb4cf2192c213e4dba1733bbcdc94cf6d85bf7
- Affected versionversion=801a6e0af0c6cedca2e99155e343ad385a50f08e <dadf9116108315f2eb14c7415c7805f392c476b4
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.
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