OPP: Fix cleanup ordering
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 173e02d674946ff3ef8da7f44a9d5b820b9af21c · fixed in f0c4b7ca24d2e2618a70826881d69b237e36bcc0; From 173e02d674946ff3ef8da7f44a9d5b820b9af21c · fixed in ce46fede7792cedd247e34b48bc8a02eb90c7848
- Linux Linux
6.19
- KernelLinux
From 6.19.0 · fixed in 7.2.6