OPP: Fix cleanup ordering
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
OPP: Fix cleanup ordering
Commit 173e02d67494 ("OPP: Initialize scope-based pointers inline") added initialization for all pointers. In some cases, the ordering was changed so that *opp_table was initialized after *opp. This also changes the order of the registered cleanup functions.
When the cleanup happens, this can cause use-after-free errors when the last reference is released and the release function _opp_kref_release tries to access the already freed opp->opp_table.
Initialize *opp_table before *opp again to fix this and ensure the correct cleanup order.
From the CVE record · Linux
The Linux kernel’s OPP cleanup can release an OPP table before an OPP object that still references it, causing a use-after-free. The input does not specify how an attacker could trigger this or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check whether their build includes the affected OPP pointer-initialization change; affected versions are not specified.