It was discovered that when exec'ing from a non-leader thread, armed POSIX CPU timers would be left on a list but freed, leading to a use-after-free.
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://ubuntu.com/security/notices/USN-5566-1 | third party advisory |
| https://ubuntu.com/security/notices/USN-5564-1 | third party advisory |
| https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2585 | third party advisory issue tracking |
| https://ubuntu.com/security/notices/USN-5567-1 | third party advisory |
| https://lore.kernel.org/lkml/20220809170751.164716-1-cascardo@canonical.com/T/#u | patch mailing list issue tracking |
| https://www.openwall.com/lists/oss-security/2022/08/09/7 | issue tracking mailing list |
| https://ubuntu.com/security/notices/USN-5565-1 | third party advisory |