Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-37968iio: light: opt3001: fix deadlock due to concurrent flag access

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 34 days later

    Published

  3. · 12 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-37968, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 94a9b7b1809f56cfaa080e70ec49b6979563a237 – < a9c56ccb7cddfca754291fb24b108a5350a5fbe9
    • affected 94a9b7b1809f56cfaa080e70ec49b6979563a237 – < 957e8be112636d9bc692917286e81e54bd87decc
    • affected 94a9b7b1809f56cfaa080e70ec49b6979563a237 – < 1d7def97e7eb65865ccc01bbdf4eb9e6bbe8a5b5
    • affected 94a9b7b1809f56cfaa080e70ec49b6979563a237 – < 748ebd8e61d0bc182c331b8df3887af7285c8a8f
    • affected 94a9b7b1809f56cfaa080e70ec49b6979563a237 – < e791bf216c9e236b34dabf514ec0ede140cca719
    • affected 94a9b7b1809f56cfaa080e70ec49b6979563a237 – < 7ca84f6a22d50bf8b31efe9eb05f9859947266d7
    • affected 94a9b7b1809f56cfaa080e70ec49b6979563a237 – < 2c95c8f0959d0a72575eabf2ff888f47ed6d8b77
    • affected 94a9b7b1809f56cfaa080e70ec49b6979563a237 – < f063a28002e3350088b4577c5640882bf4ea17ea
  • Linux · Linux

    • affected 4.3
    • unaffected < 4.3
    • unaffected 5.4.299 – ≤ 5.4.*
    • unaffected 5.10.243 – ≤ 5.10.*
    • unaffected 5.15.192 – ≤ 5.15.*
    • unaffected 6.1.151 – ≤ 6.1.*
    • unaffected 6.6.105 – ≤ 6.6.*
    • unaffected 6.12.30 – ≤ 6.12.*
    • unaffected 6.14.7 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-37968 badge
[![CVE-2025-37968](https://cveledger.app/badge/CVE-2025-37968.svg)](https://cveledger.app/cve/CVE-2025-37968)

Record last updated .