VDB

CVE-2025-37968

CVE-2025-37968 PUBLISHED

iio: light: opt3001: fix deadlock due to concurrent flag access

Reported by linux · Published May 20, 2025

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.

Affected products

VendorProductVersions
LinuxLinux94a9b7b1809f56cfaa080e70ec49b6979563a237, 94a9b7b1809f56cfaa080e70ec49b6979563a237, 94a9b7b1809f56cfaa080e70ec49b6979563a237
LinuxLinux4.3, 0, 5.4.299
linuxlinux_kernel4.3, 4.3, 4.3
SiemensSIMATIC CN 41000
LinuxLinux0, 5.4.299, 5.10.243

Timeline

  • May 20, 2025 CVE Published
  • May 21, 2025 EPSS Score (30 in total, the first dated here)
  • Oct 12, 2025 PoC Published (7 in total, the first dated here)
  • Mar 29, 2026 Distribution Patch (241 in total, the first dated here)
  • Mar 29, 2026 Security Advisory (249 in total, the first dated here)
  • Jun 9, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-37968
vulnetix vdb fixes CVE-2025-37968

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-37968/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›