OPP: Fix race between OPP addition and lookup
CVE-2026-74405 · published 15 Aug 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-74405?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 7034764a1e4a6edbb60914e89aad8384e3fe5d17 to < 932ebfad767be1395946cbc1727a7c38eeee3d24, 7034764a1e4a6edbb60914e89aad8384e3fe5d17 to < 1946ea2f6b3ec00e313c78e83fc196f1f6aba2a9, 7034764a1e4a6edbb60914e89aad8384e3fe5d17 to < 46696b0b2123475d7f95909435c09808fc5ffd23, 7034764a1e4a6edbb60914e89aad8384e3fe5d17 to < bb75bd7d9ae7672034f73ce67a57e6ac89bb39e5
- Linux Linux: 4.11
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
OPP: Fix race between OPP addition and lookup
A race exists between dev_pm_opp_add_dynamic() and
dev_pm_opp_find_freq_exact():
CPU0 (add) CPU1 (lookup)
------------------------------- ------------------------------
_opp_add()
mutex_lock()
list_add(&new_opp->node, head)
mutex_unlock() _opp_table_find_key()
mutex_lock()
dev_pm_opp_get(opp)
kref_get()
mutex_unlock()
kref_init(&new_opp->kref)
dev_pm_opp_put()
kref_put_mutex()
The newly added OPP is inserted into the list before its kref is
initialized. A concurrent lookup can find this OPP and increment its
reference count while it is still uninitialized, leading to refcount
corruption and a potential premature free.
Fix this by initializing ->kref and ->opp_table before making the OPP
visible via list_add(). This ensures any concurrent lookup observes a
fully initialized object.
[ Viresh: Updated commit log ]
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/932ebfad767be1395946cbc1727a7c38eeee3d24
- git.kernel.org/stable/c/1946ea2f6b3ec00e313c78e83fc196f1f6aba2a9
- git.kernel.org/stable/c/46696b0b2123475d7f95909435c09808fc5ffd23
- git.kernel.org/stable/c/bb75bd7d9ae7672034f73ce67a57e6ac89bb39e5
- git.kernel.org/stable/c/f5e1cc9a284bff2510981643a5bca4bc4c21b81a
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON