The reference count changes made as part of the CVE-2023-33951 and CVE-2023-33952 fixes exposed a use-after-free flaw in the way memory objects were handled when they were being used to store a surface. When running inside a VMware guest with 3D acceleration enabled, a local, unprivileged user could potentially use this flaw to escalate their privileges.
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/errata/RHSA-2024:0113 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2024:0134 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2024:0461 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2024:1404 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2024:4823 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2024:4831 | third party advisory vendor advisory |
https://access.redhat.com/security/cve/CVE-2023-5633 | third party advisory vdb entry |
https://bugzilla.redhat.com/show_bug.cgi?id=2245663 | patch issue tracking |