6.4

CVE-2023-20835

In camsys, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07341261; Issue ID: ALPS07326570.

Data is provided by the National Vulnerability Database (NVD)
LinuxfoundationYocto Version4.0
   MediatekMt6895 Version-
   MediatekMt6983 Version-
   MediatekMt8188 Version-
   MediatekMt8195 Version-
   MediatekMt8395 Version-
   MediatekMt8781 Version-
MediatekIot Yocto Version23.0
   MediatekMt6895 Version-
   MediatekMt6983 Version-
   MediatekMt8188 Version-
   MediatekMt8195 Version-
   MediatekMt8395 Version-
   MediatekMt8781 Version-
GoogleAndroid Version12.0
   MediatekMt6895 Version-
   MediatekMt6983 Version-
   MediatekMt8188 Version-
   MediatekMt8195 Version-
   MediatekMt8395 Version-
   MediatekMt8781 Version-
GoogleAndroid Version13.0
   MediatekMt6895 Version-
   MediatekMt6983 Version-
   MediatekMt8188 Version-
   MediatekMt8195 Version-
   MediatekMt8395 Version-
   MediatekMt8781 Version-
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
EPSS Metriken
Type Source Score Percentile
EPSS FIRST.org 0.02% 0.027
CVSS Metriken
Source Base Score Exploit Score Impact Score Vector string
nvd@nist.gov 6.4 0.5 5.9
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
134c704f-9b21-4f2e-91b3-4a467353bcc0 6.4 0.5 5.9
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

CWE-416 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.