Answer in brief
CVE-2026-74405 records a Unknown severity vulnerability in OPP: Fix race between OPP addition and lookup. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7034764a1e4a6edbb60914e89aad8384e3fe5d17 <46696b0b2123475d7f95909435c09808fc5ffd23 || >=7034764a1e4a6edbb60914e89aad8384e3fe5d17 <bb75bd7d9ae7672034f73ce67a57e6ac89bb39e5 || >=7034764a1e4a6edbb60914e89aad8384e3fe5d17 <f5e1cc9a284bff2510981643a5bca4bc4c21b81a | 46696b0b2123475d7f95909435c09808fc5ffd23, bb75bd7d9ae7672034f73ce67a57e6ac89bb39e5, f5e1cc9a284bff2510981643a5bca4bc4c21b81a |
| Linux/Linuxgeneric | 4.11 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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 ]
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74405 records a Unknown severity vulnerability in OPP: Fix race between OPP addition and lookup. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7034764a1e4a6edbb60914e89aad8384e3fe5d17 <46696b0b2123475d7f95909435c09808fc5ffd23 || >=7034764a1e4a6edbb60914e89aad8384e3fe5d17 <bb75bd7d9ae7672034f73ce67a57e6ac89bb39e5 || >=7034764a1e4a6edbb60914e89aad8384e3fe5d17 <f5e1cc9a284bff2510981643a5bca4bc4c21b81a | 46696b0b2123475d7f95909435c09808fc5ffd23, bb75bd7d9ae7672034f73ce67a57e6ac89bb39e5, f5e1cc9a284bff2510981643a5bca4bc4c21b81a |
| Linux/Linuxgeneric | 4.11 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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 ]
Quoted source text, attributed separately from HOL analysis.