CVE-2026-74405

HIGHCVSS 7.8/10EPSS 0.13%

Last modified

CVE-2026-74405 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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(). EPSS estimates a 0.13% chance of exploitation in the next 30 days.

Description

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 ]

Metrics

EPSS Probability
0.13%

2.5th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < 835b9b5b4d287a03c713680b0231d36ff599201b; >= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < 2fb061a90898420d8ca1a0b9959ca977d90fa841; >= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < e25be5d812ec8ca2615d23726b3861b04e2fff35; >= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < 932ebfad767be1395946cbc1727a7c38eeee3d24; >= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < 1946ea2f6b3ec00e313c78e83fc196f1f6aba2a9; >= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < 46696b0b2123475d7f95909435c09808fc5ffd23; >= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < bb75bd7d9ae7672034f73ce67a57e6ac89bb39e5; >= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < f5e1cc9a284bff2510981643a5bca4bc4c21b81a
LinuxLinux4.11

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-74405?
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 ]
How severe is CVE-2026-74405?
CVE-2026-74405 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.13% probability of exploitation in the next 30 days.
How do I fix CVE-2026-74405?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-74405?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST