CVE-2025-37968: iio: light: opt3001: fix deadlock due to concurrent flag access
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.16% (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 1d7def97e7eb65865ccc01bbdf4eb9e6bbe8a5b5, 2c95c8f0959d0a72575eabf2ff888f47ed6d8b77, 748ebd8e61d0bc182c331b8df3887af7285c8a8f.
Low priority for now. Upgrade to Linux Linux 1d7def97e7eb65865ccc01bbdf4eb9e6bbe8a5b5, 2c95c8f0959d0a72575eabf2ff888f47ed6d8b77, 748ebd8e61d0bc182c331b8df3887af7285c8a8f 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: light: opt3001: fix deadlock due to concurrent flag access The threaded IRQ function in this driver is reading the flag twice: once to lock a mutex and once to unlock it. Even though the code setting the flag is designed to prevent it, there are subtle cases where the flag could be true at the mutex_lock stage and false at the mutex_unlock stage. This results in the mutex not being unlocked, resulting in a deadlock. Fix it by making the opt3001_irq() code generally more robust, reading the flag into a variable and using the variable value at both stages.
- Published
- May 20, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 5th 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.3affected
- 94a9b7b1809f56cfaa080e70ec49b6979563a237 and later · before a9c56ccb7cddfca754291fb24b108a5350a5fbe9affected · git
- 94a9b7b1809f56cfaa080e70ec49b6979563a237 and later · before 957e8be112636d9bc692917286e81e54bd87deccaffected · git
- 94a9b7b1809f56cfaa080e70ec49b6979563a237 and later · before 1d7def97e7eb65865ccc01bbdf4eb9e6bbe8a5b5affected · git
- 94a9b7b1809f56cfaa080e70ec49b6979563a237 and later · before 748ebd8e61d0bc182c331b8df3887af7285c8a8faffected · git
- 94a9b7b1809f56cfaa080e70ec49b6979563a237 and later · before e791bf216c9e236b34dabf514ec0ede140cca719affected · git
- 94a9b7b1809f56cfaa080e70ec49b6979563a237 and later · before 7ca84f6a22d50bf8b31efe9eb05f9859947266d7affected · git
- 94a9b7b1809f56cfaa080e70ec49b6979563a237 and later · before 2c95c8f0959d0a72575eabf2ff888f47ed6d8b77affected · git
- 94a9b7b1809f56cfaa080e70ec49b6979563a237 and later · before f063a28002e3350088b4577c5640882bf4ea17eaaffected · git
- before 4.3not 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.243
- linux linux kernel5.11 and later · before 5.15.192
- linux linux kernel5.16 and later · before 6.1.151
- linux linux kernel4.3 and later · before 5.4.299
- linux linux kernel6.7 and later · before 6.12.30
- linux linux kernel6.13 and later · before 6.14.7
- linux linux kernel6.2 and later · before 6.6.105
- 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:11 | linux-6.1 | before 6.1.153-1~deb11u1 | 6.1.153-1~deb11u1 |
| Debian:12 | linux | before 6.1.153-1 | 6.1.153-1 |
| Debian:13 | linux | before 6.12.30-1 | 6.12.30-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-37965May 20, 2025 · drm/amd/display: Fix invalid context error in dml helper22Monitor
- ← EarlierCVE-2025-37966May 20, 2025 · riscv: Fix kernel crash due to PR_SET_TAGGED_ADDR_CTRL22Monitor
- Later →CVE-2025-37969May 20, 2025 · iio: imu: st_lsm6dsx: fix possible lockup in st_lsm6dsx_read_tagged_fifo22Monitor
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 | 1d7def97e7eb65865ccc01bbdf4eb9e6bbe8a5b5 | Vendor (CNA) |
| Linux Linux | 2c95c8f0959d0a72575eabf2ff888f47ed6d8b77 | Vendor (CNA) |
| Linux Linux | 748ebd8e61d0bc182c331b8df3887af7285c8a8f | Vendor (CNA) |
| Linux Linux | 7ca84f6a22d50bf8b31efe9eb05f9859947266d7 | Vendor (CNA) |
| Linux Linux | 957e8be112636d9bc692917286e81e54bd87decc | Vendor (CNA) |
| Linux Linux | a9c56ccb7cddfca754291fb24b108a5350a5fbe9 | Vendor (CNA) |
| Linux Linux | e791bf216c9e236b34dabf514ec0ede140cca719 | Vendor (CNA) |
| Linux Linux | f063a28002e3350088b4577c5640882bf4ea17ea | Vendor (CNA) |
| debian:linux | 6.1.153-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.1 | 6.1.153-1~deb11u1 · Debian:11 | 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 (10 more)Show less
- git.kernel.org/stable/c/2c95c8f0959d0a72575eabf2ff888f47ed6d8b77
- git.kernel.org/stable/c/748ebd8e61d0bc182c331b8df3887af7285c8a8f
- git.kernel.org/stable/c/7ca84f6a22d50bf8b31efe9eb05f9859947266d7
- git.kernel.org/stable/c/957e8be112636d9bc692917286e81e54bd87decc
- git.kernel.org/stable/c/a9c56ccb7cddfca754291fb24b108a5350a5fbe9
- git.kernel.org/stable/c/e791bf216c9e236b34dabf514ec0ede140cca719
- git.kernel.org/stable/c/f063a28002e3350088b4577c5640882bf4ea17ea
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
- cert-portal.siemens.com/productcert/html/ssa-032379.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.