A use-after-free flaw was found in PackageKitd. In some conditions, the order of cleanup mechanics for a transaction could be impacted. As a result, some memory access could occur on memory regions that were previously freed. Once freed, a memory region can be reused for other allocations and any previously stored data in this memory region is considered lost.
Workaround:
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
| Link | Tags |
|---|---|
| https://access.redhat.com/security/cve/CVE-2024-0217 | mitigation third party advisory vdb entry |
| https://bugzilla.redhat.com/show_bug.cgi?id=2256624 | patch third party advisory issue tracking |
| https://github.com/PackageKit/PackageKit/commit/64278c9127e3333342b56ead99556161f7e86f79 | patch |