Memory corruption during concurrent access to server info object due to incorrect reference count update.
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://docs.qualcomm.com/product/publicresources/securitybulletin/may-2025-bulletin.html | patch vendor advisory |