CVE-2025-37970: iio: imu: st_lsm6dsx: fix possible lockup in st_lsm6dsx_read_fifo
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 159ca7f18129834b6f4c7eae67de48e96c752fc9, 3bb6c02d6fe8347ce1785016d135ff539c20043c, 6c4a5000618a8c44200d455c92e2f2a4db264717; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.
Low priority for now. Upgrade to Linux Linux 159ca7f18129834b6f4c7eae67de48e96c752fc9, 3bb6c02d6fe8347ce1785016d135ff539c20043c, 6c4a5000618a8c44200d455c92e2f2a4db264717; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: iio: imu: st_lsm6dsx: fix possible lockup in st_lsm6dsx_read_fifo Prevent st_lsm6dsx_read_fifo from falling in an infinite loop in case pattern_len is equal to zero and the device FIFO is not empty.
- Published
- May 20, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-667
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.11affected
- 290a6ce11d938be52634b3ce1bbc6b78be4d23c1 and later · before f06a1a1954527cc4ed086d926c81ff236b2adde9affected · git
- 290a6ce11d938be52634b3ce1bbc6b78be4d23c1 and later · before 84e39f628a3a3333add99076e4d6c8b42b12d3a0affected · git
- 290a6ce11d938be52634b3ce1bbc6b78be4d23c1 and later · before f3cf233c946531a92fe651ff2bd15ebbe60630a7affected · git
- 290a6ce11d938be52634b3ce1bbc6b78be4d23c1 and later · before 6c4a5000618a8c44200d455c92e2f2a4db264717affected · git
- 290a6ce11d938be52634b3ce1bbc6b78be4d23c1 and later · before da33c4167b9cc1266a97215114cb74679f881d0caffected · git
- 290a6ce11d938be52634b3ce1bbc6b78be4d23c1 and later · before a1cad8a3bca41dead9980615d35efc7bff1fd534affected · git
- 290a6ce11d938be52634b3ce1bbc6b78be4d23c1 and later · before 3bb6c02d6fe8347ce1785016d135ff539c20043caffected · git
- 290a6ce11d938be52634b3ce1bbc6b78be4d23c1 and later · before 159ca7f18129834b6f4c7eae67de48e96c752fc9affected · git
- before 4.11not affected · semver
Affected versions · NVD (9)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.5 and later · before 5.10.238
- linux linux kernel5.11 and later · before 5.15.183
- linux linux kernel5.16 and later · before 6.1.139
- linux linux kernel4.11 and later · before 5.4.294
- linux linux kernel6.7 and later · before 6.12.29
- linux linux kernel6.13 and later · before 6.14.7
- linux linux kernel6.2 and later · before 6.6.91
- linux linux kernel6.15
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.140-1 | 6.1.140-1 |
| Debian:13 | linux | before 6.12.29-1 | 6.12.29-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-37968May 20, 2025 · iio: light: opt3001: fix deadlock due to concurrent flag access22Monitor
- ← EarlierCVE-2025-37969May 20, 2025 · iio: imu: st_lsm6dsx: fix possible lockup in st_lsm6dsx_read_tagged_fifo22Monitor
- Later →CVE-2025-37971May 20, 2025 · staging: bcm2835-camera: Initialise dev in v4l2_dev22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 159ca7f18129834b6f4c7eae67de48e96c752fc9 | Vendor (CNA) |
| Linux Linux | 3bb6c02d6fe8347ce1785016d135ff539c20043c | Vendor (CNA) |
| Linux Linux | 6c4a5000618a8c44200d455c92e2f2a4db264717 | Vendor (CNA) |
| Linux Linux | 84e39f628a3a3333add99076e4d6c8b42b12d3a0 | Vendor (CNA) |
| Linux Linux | a1cad8a3bca41dead9980615d35efc7bff1fd534 | Vendor (CNA) |
| Linux Linux | da33c4167b9cc1266a97215114cb74679f881d0c | Vendor (CNA) |
| Linux Linux | f06a1a1954527cc4ed086d926c81ff236b2adde9 | Vendor (CNA) |
| Linux Linux | f3cf233c946531a92fe651ff2bd15ebbe60630a7 | Vendor (CNA) |
| azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.140-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/3bb6c02d6fe8347ce1785016d135ff539c20043c
- git.kernel.org/stable/c/6c4a5000618a8c44200d455c92e2f2a4db264717
- git.kernel.org/stable/c/84e39f628a3a3333add99076e4d6c8b42b12d3a0
- git.kernel.org/stable/c/a1cad8a3bca41dead9980615d35efc7bff1fd534
- git.kernel.org/stable/c/da33c4167b9cc1266a97215114cb74679f881d0c
- git.kernel.org/stable/c/f06a1a1954527cc4ed086d926c81ff236b2adde9
- git.kernel.org/stable/c/f3cf233c946531a92fe651ff2bd15ebbe60630a7
- lists.debian.org/debian-lts-announce/2025/08/msg00010.html
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.