Linux
OPP: Fix race between OPP addition and lookup
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 ]
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < 835b9b5b4d287a03c713680b0231d36ff599201b
- >= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < 2fb061a90898420d8ca1a0b9959ca977d90fa841
- >= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < e25be5d812ec8ca2615d23726b3861b04e2fff35
- >= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < 932ebfad767be1395946cbc1727a7c38eeee3d24
- >= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < 1946ea2f6b3ec00e313c78e83fc196f1f6aba2a9
- >= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < 46696b0b2123475d7f95909435c09808fc5ffd23
- >= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < bb75bd7d9ae7672034f73ce67a57e6ac89bb39e5
- >= 7034764a1e4a6edbb60914e89aad8384e3fe5d17, < f5e1cc9a284bff2510981643a5bca4bc4c21b81a
Fixed in 835b9b5b4d287a03c713680b0231d36ff599201b, 2fb061a90898420d8ca1a0b9959ca977d90fa841, e25be5d812ec8ca2615d23726b3861b04e2fff35, 932ebfad767be1395946cbc1727a7c38eeee3d24, 1946ea2f6b3ec00e313c78e83fc196f1f6aba2a9, 46696b0b2123475d7f95909435c09808fc5ffd23, bb75bd7d9ae7672034f73ce67a57e6ac89bb39e5, f5e1cc9a284bff2510981643a5bca4bc4c21b81a
- 4.11
Fixed in 0, 5.10.273, 5.15.224, 6.1.191, 6.6.160, 6.12.114, 6.18.40, 7.1.5, 7.2
Mitigation
Upgrade Linux to 835b9b5b4d287a03c713680b0231d36ff599201b or 2fb061a90898420d8ca1a0b9959ca977d90fa841 or e25be5d812ec8ca2615d23726b3861b04e2fff35 or 932ebfad767be1395946cbc1727a7c38eeee3d24 or 1946ea2f6b3ec00e313c78e83fc196f1f6aba2a9 or 46696b0b2123475d7f95909435c09808fc5ffd23 or bb75bd7d9ae7672034f73ce67a57e6ac89bb39e5 or f5e1cc9a284bff2510981643a5bca4bc4c21b81a or later.
Upgrade Linux to 0 or 5.10.273 or 5.15.224 or 6.1.191 or 6.6.160 or 6.12.114 or 6.18.40 or 7.1.5 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.