CVE-2022-22095

HighCVSS 7.8/10Last modified Jun 17, 2026

Description

Memory corruption in synx driver due to use-after-free condition in the synx driver due to accessing object handles without acquiring lock in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile

Metrics

CVSS 3.1 7.8/10CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Weakness enumeration

CWE-416

Affected software

No affected versions have been published.

Timeline

Published: Sep 16, 2022
Last modified: Jun 17, 2026
NVD status: Modified

Related CVEs from 2022

CVE-2022-220969.8Memory corruption in Bluetooth HOST due to stack-based buffer overflow when when extracting data using command length parameter in Snapdrago CVE-2022-220977.8Memory corruption in graphic driver due to use after free while calling multiple threads application to driver. in Snapdragon Consumer IOT CVE-2022-220987.8Memory corruption in multimedia driver due to untrusted pointer dereference while reading data from socket in Snapdragon Auto CVE-2022-220997.8Memory corruption in multimedia due to improper validation of array index in Snapdragon Auto CVE-2022-22107.8Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.CVE-2022-221007.8Memory corruption in multimedia due to improper check on received export descriptors in Snapdragon Auto CVE-2022-221015.5Denial of service in multimedia due to uncontrolled resource consumption while parsing an incoming HAB message in Snapdragon Auto CVE-2022-221027.8Memory corruption in multimedia due to incorrect type conversion while adding data in Snapdragon Auto CVE-2022-221037.8Memory corruption in multimedia driver due to double free while processing data from user in Snapdragon Auto CVE-2022-221047.8Memory corruption in multimedia due to improper check on the messages received. in Snapdragon Auto CVE-2022-221059.8Memory corruption in bluetooth due to integer overflow while processing HFP-UNIT profile in Snapdragon Auto, Snapdragon Consumer IOT, Snapdr CVE-2022-221067.8Memory corruption in multimedia due to improper length check while copying the data in Snapdragon Auto