CPE Details
Qualcomm VIDEO COLLABORATION VC1 PLATFORM Firmware
-
2024-12-20
14h08 +00:00
14h08 +00:00
2024-12-20
14h08 +00:00
14h08 +00:00
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
CPE Name: cpe:2.3:o:qualcomm:video_collaboration_vc1_platform_firmware:-:*:*:*:*:*:*:*
Informations
Vendor
qualcommProduct
video_collaboration_vc1_platform_firmwareVersion
-Related CVE
| CVE ID | Publié | Description | Score | Gravité |
|---|---|---|---|---|
| Memory corruption while processing IOCTL from user space to handle GPU AHB bus error. | 7.8 |
Haute |
||
| Information disclosure while parsing the OCI IE with invalid length. | 8.2 |
Haute |
||
| Memory corruption while power-up or power-down sequence of the camera sensor. | 7.8 |
Haute |
||
| Memory corruption can occur when a compat IOCTL call is followed by a normal IOCTL call from userspace. | 7.8 |
Haute |
||
| Memory corruption while parsing the memory map info in IOCTL calls. | 7.8 |
Haute |
||
| Information disclosure while processing IO control commands. | 6.1 |
Moyen |
||
| Information disclosure during audio playback. | 6.1 |
Moyen |
||
| Memory corruption when allocating and accessing an entry in an SMEM partition continuously. | 8.4 |
Haute |
||
| Memory corruption when multiple threads try to unregister the CVP buffer at the same time. | 6.7 |
Moyen |
||
| Memory corruption while Configuring the SMR/S2CR register in Bypass mode. | 8.4 |
Haute |
||
| Information disclosure as NPU firmware can send invalid IPC message to NPU driver as the driver doesn`t validate the IPC message received from the firmware. | 6.1 |
Moyen |
||
| Memory corruption while parsing sensor packets in camera driver, user-space variable is used while allocating memory in kernel and parsing which can lead to huge allocation or invalid memory access. | 6.7 |
Moyen |
||
| Memory corruption during GNSS HAL process initialization. | 7.8 |
Haute |
||
| Memory corruption while processing GPU page table switch. | 7.8 |
Haute |
||
| Memory corruption while processing voice packet with arbitrary data received from ADSP. | 7.8 |
Haute |
||
| Memory corruption while processing GPU commands. | 7.8 |
Haute |
||
| Memory corruption while invoking IOCTL calls from the use-space for HGSL memory node. | 7.8 |
Haute |
||
| Memory corruption while handling session errors from firmware. | 7.8 |
Haute |
||
| Cryptographic issue when a controller receives an LMP start encryption command under unexpected conditions. | 9.1 |
Critique |
||
| Memory corruption when the user application modifies the same shared memory asynchronously when kernel is accessing it. | 6.7 |
Moyen |
||
| Transient DOS while handling PS event when Program Service name length offset value is set to 255. | 5.5 |
Moyen |
||
| Memory corruption can occur if VBOs hold outdated or invalid GPU SMMU mappings, especially when the binding and reclaiming of memory buffers are performed at the same time. | 8.4 |
Haute |
||
| Memory corruption as fence object may still be accessed in timeline destruct after isync fence is released. | 8.4 |
Haute |
||
| Memory corruption can occur when arbitrary user-space app gains kernel level privilege to modify DDR memory by corrupting the GPU page table. | 8.4 |
Haute |
||
| Memory corruption while creating a fence to wait on timeline events, and simultaneously signal timeline events. | 8.4 |
Haute |
||
| Memory corruption while allocating memory in HGSL driver. | 8.4 |
Haute |
||
| Memory corruption while processing IOCTL call to set metainfo. | 8.4 |
Haute |
||
| Transient DOS while parsing SCAN RNR IE when bytes received from AP is such that the size of the last param of IE is less than neighbor report. | 7.5 |
Haute |
||
| Transient DOS while parsing ESP IE from beacon/probe response frame. | 7.5 |
Haute |
||
| Transient DOS while parsing the multiple MBSSID IEs from the beacon, when the tag length is non-zero value but with end of beacon. | 7.5 |
Haute |
||
| Transient DOS while parsing the MBSSID IE from the beacons, when the MBSSID IE length is zero. | 7.5 |
Haute |
||
| Transient DOS while parsing fragments of MBSSID IE from beacon frame. | 7.5 |
Haute |
||
| Memory corruption when the mapped pages in VBO are still mapped after reclaiming by shrinker. | 8.4 |
Haute |
||
| Memory corruption when kernel driver attempts to trigger hardware fences. | 8.4 |
Haute |
||
| Memory corruption while processing graphics kernel driver request to create DMA fence. | 8.4 |
Haute |
||
| Memory corruption when memory mapped in a VBO is not unmapped by the GPU SMMU. | 8.4 |
Haute |
||
| Transient DOS while importing a PKCS#8-encoded RSA key with zero bytes modulus. | 6.2 |
Moyen |
||
| Memory corruption during session sign renewal request calls in HLOS. | 7.8 |
Haute |
||
| Transient DOS while decoding attach reject message received by UE, when IEI is set to ESM_IEI. | 7.5 |
Haute |
||
| Transient DOS during music playback of ALAC content. | 7.5 |
Haute |
||
| Information disclosure while handling beacon or probe response frame in STA. | 7.5 |
Haute |
||
| Memory corruption while handling user packets during VBO bind operation. | 8.4 |
Haute |
||
| Memory corruption when IOMMU unmap operation fails, the DMA and anon buffers are getting released. | 8.4 |
Haute |
||
| Memory corruption while invoking IOCTL call for GPU memory allocation and size param is greater than expected size. | 8.4 |
Haute |
||
| Memory corruption when allocating and accessing an entry in an SMEM partition. | 7.8 |
Haute |
||
| Memory corruption while processing key blob passed by the user. | 7.8 |
Haute |
||
| Transient DOS while loading the TA ELF file. | 7.1 |
Haute |
||
| Memory corruption while performing finish HMAC operation when context is freed by keymaster. | 8.4 |
Haute |
Les informations affichées sur CVE Find proviennent de plusieurs sources de référence rigoureusement sélectionnées. Les données CVE sont fournies par MITRE Corporation et la National Vulnerability Database (NVD). Le catalogue des vulnérabilités activement exploitées (KEV) provient de la Cybersecurity and Infrastructure Security Agency (CISA), tandis que les scores EPSS sont issus de FIRST.org. Enfin, les données relatives aux faiblesses logicielles (CWE) et aux schémas d'attaque courants (CAPEC)
sont maintenues par MITRE Corporation, et les informations sur les configurations
logicielles et matérielles (CPE) proviennent du NVD.