CVE-2025-37968
iio: light: opt3001: fix deadlock due to concurrent flag access
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.3
References 8
git.kernel.org
- stable/c/a9c56ccb7cddfca754291fb24b108a5350a5fbe9
- stable/c/957e8be112636d9bc692917286e81e54bd87decc
- stable/c/1d7def97e7eb65865ccc01bbdf4eb9e6bbe8a5b5
- stable/c/748ebd8e61d0bc182c331b8df3887af7285c8a8f
- stable/c/e791bf216c9e236b34dabf514ec0ede140cca719
- stable/c/7ca84f6a22d50bf8b31efe9eb05f9859947266d7
- stable/c/2c95c8f0959d0a72575eabf2ff888f47ed6d8b77
- stable/c/f063a28002e3350088b4577c5640882bf4ea17ea