CPE Details
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
CPE Name: cpe:2.3:h:qualcomm:sa8530p:-:*:*:*:*:*:*:*
Informations
Vendor
qualcommProduct
sa8530pVersion
-Related CVE
| CVE ID | Publié | Description | Score | Gravité |
|---|---|---|---|---|
| Transient DOS may occur while processing the country IE. | 7.5 |
Haute |
||
| Memory corruption in display driver while detaching a device. | 7.8 |
Haute |
||
| Memory corruption may occur while validating ports and channels in Audio driver. | 7.8 |
Haute |
||
| Information disclosure while deriving keys for a session for any Widevine use case. | 5.5 |
Moyen |
||
| Memory corruption during management frame processing due to mismatch in T2LM info element. | 9.8 |
Critique |
||
| Information disclosure while parsing the OCI IE with invalid length. | 8.2 |
Haute |
||
| Memory corruption while parsing the ML IE due to invalid frame content. | 9.8 |
Critique |
||
| 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 |
||
| Information disclosure while processing information on firmware image during core initialization. | 6.1 |
Moyen |
||
| Transient DOS can occur when the driver parses the per STA profile IE and tries to access the EXTN element ID without checking the IE length. | 7.5 |
Haute |
||
| Information disclosure while invoking callback function of sound model driver from ADSP for every valid opcode received from sound model driver. | 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 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 handling session errors from firmware. | 7.8 |
Haute |
||
| Transient DOS while processing the CU information from RNR IE. | 7.5 |
Haute |
||
| Memory corruption when the user application modifies the same shared memory asynchronously when kernel is accessing it. | 6.7 |
Moyen |
||
| Transient DOS when transmission of management frame sent by host is not successful and error status is received in the host. | 7.5 |
Haute |
||
| Transient DOS while parsing noninheritance IE of Extension element when length of IE is 2 of beacon frame. | 7.5 |
Haute |
||
| Memory corruption when invalid length is provided from HLOS for FRS/UDS request/response buffers. | 7.8 |
Haute |
||
| Transient DOS while parsing the multi-link element Control field when common information length check is missing before updating the location. | 7.5 |
Haute |
||
| Transient DOS while parsing MBSSID during new IE generation in beacon/probe frame when IE length check is either missing or improper. | 7.5 |
Haute |
||
| Memory corruption when BTFM client sends new messages over Slimbus to ADSP. | 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 while creating a fence to wait on timeline events, and simultaneously signal timeline events. | 8.4 |
Haute |
||
| Memory corruption while processing IOCTL call to set metainfo. | 8.4 |
Haute |
||
| Transient DOS while parsing the received TID-to-link mapping element of the TID-to-link mapping action frame. | 7.5 |
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 |
||
| 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 |
||
| Memory corruption when keymaster operation imports a shared key. | 7.8 |
Haute |
||
| Transient DOS during music playback of ALAC content. | 7.5 |
Haute |
||
| Memory corruption when IOMMU unmap operation fails, the DMA and anon buffers are getting released. | 8.4 |
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 |
||
| Memory corruption while playing audio file having large-sized input buffer. | 9.8 |
Critique |
||
| Memory corruption when the payload received from firmware is not as per the expected protocol size. | 7.8 |
Haute |
||
| Memory corruption when size of buffer from previous call is used without validation or re-initialization. | 8.4 |
Haute |
||
| Memory corruption when IOMMU unmap of a GPU buffer fails in Linux. | 8.4 |
Haute |
||
| Memory corruption while verifying the serialized header when the key pairs are generated. | 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.