Security Vulnerabilities
- CVEs Published In August 2023
The buffer obtained from kernel APIs such as cam_mem_get_cpu_buf() may be readable/writable in userspace after kernel accesses it. In other words, user mode may race and modify the packet header (e.g. header.count), causing checks (e.g. size checks) in kernel code to be invalid. This may lead to out-of-bounds read/write issues.
In the function call related to CAM_REQ_MGR_RELEASE_BUF there is no check if the buffer is being used. So when a function called cam_mem_get_cpu_buf to get the kernel va to use, another thread can call CAM_REQ_MGR_RELEASE_BUF to unmap the kernel va which cause UAF of the kernel address.
A vulnerability has been identified in JT2Go (All versions < V14.2.0.5), Solid Edge SE2022 (All versions < V222.0 Update 13), Solid Edge SE2023 (All versions < V223.0 Update 4), Teamcenter Visualization V13.2 (All versions < V13.2.0.15), Teamcenter Visualization V13.3 (All versions < V13.3.0.11), Teamcenter Visualization V14.1 (All versions < V14.1.0.11), Teamcenter Visualization V14.2 (All versions < V14.2.0.5). The affected application contains a use-after-free vulnerability that could be triggered while parsing specially crafted ASM file. An attacker could leverage this vulnerability to execute code in the context of the current process.
Information disclosure in Network Services due to buffer over-read while the device receives DNS response.
Cryptographic issue in HLOS due to improper authentication while performing key velocity checks using more than one key.
Memory corruption in Trusted Execution Environment while calling service API with invalid address.
Memory corruption due to untrusted pointer dereference in automotive during system call.
Information disclosure in Bluetooth when an GATT packet is received due to improper input validation.
Memory corruption in RIL while trying to send apdu packet.
Memory corruption in WLAN while running doDriverCmd for an unspecific command.