qcs8155 firmware · threatengine.sh

Home/Product/qualcomm qcs8155 firmware

Product

qualcomm qcs8155 firmware

79 known vulnerabilities across versions

Vulnerabilities are listed by affected version. Select any CVE for the full briefing and its intelligence graph.

Sort Min CVSS Published since

Memory corruption during PlayReady APP usecase while processing TA commands.

Memory corruption while handling client exceptions, allowing unauthorized channel access.

Information disclosure while processing the hash segment in an MBN file.

Information disclosure while reading data from an image using specified offset and size parameters.

Memory corruption whhile handling the subsystem failure memory during the parsing of video packets received from the video firmwar

Memory corruption while processing video packets received from video firmware.

Memory corruption while triggering commands in the PlayReady Trusted application.

Memory corruption while calling the NPU driver APIs concurrently.

Information disclosure may occur due to improper permission and access controls to Video Analytics engine.

Memory corruption when allocating and accessing an entry in an SMEM partition continuously.

Memory corruption while Configuring the SMR/S2CR register in Bypass mode.

Memory corruption while processing GPU page table switch.

memory corruption when an invalid firehose patch command is invoked.

Memory corruption when an invoke call and a TEE call are bound for the same trusted application.

Memory corruption while processing key blob passed by the user.

Transient DOS while loading the TA ELF file.

Memory corruption while performing finish HMAC operation when context is freed by keymaster.

Memory corruption while copying a keyblobs material when the key materials size is not accurately checked.

Memory corruption when the payload received from firmware is not as per the expected protocol size.

Memory corruption when there is failed unmap operation in GPU.

Memory corruption in SPS Application while requesting for public key in sorter TA.

Memory corruption while processing the event ring, the context read pointer is untrusted to HLOS and when it is passed with arbitr

Memory corruption in HLOS while converting from authorization token to HIDL vector.

Memory corruption in TZ Secure OS while requesting a memory allocation from TA region.

Memory corruption in HLOS while running playready use-case.

Memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call.

Transient DOS in Automotive OS due to improper authentication to the secure IO calls.

Memory corruption in DSP Services during a remote call from HLOS to DSP.

Memory corruption in Boot while running a ListVars test in UEFI Menu during boot.

Information disclosure when the trusted application metadata symbol addresses are accessed while loading an ELF in TEE.

Memory corruption while loading an ELF segment in TEE Kernel.

Memory Corruption in SPS Application while exporting public key in sorter TA.

Memory Corruption in camera while installing a fd for a particular DMA buffer.

Cryptographic issue in HLOS during key management.

Information Disclosure in Qualcomm IPC while reading values from shared memory in VM.

Memory Corruption in Core due to secure memory access by user while loading modem image.

Memory Corruption in HLOS while registering for key provisioning notify.

Memory corruption in WIN Product while invoking WinAcpi update driver in the UEFI region.

Memory Corruption in Core Platform while printing the response buffer in log.

Memory corruption in Core Platform while printing the response buffer in log.

The cam_get_device_priv function does not check the type of handle being returned (device/session/link). This would lead to invali

Memory corruption in Trusted Execution Environment while calling service API with invalid address.

Cryptographic issue in HLOS due to improper authentication while performing key velocity checks using more than one key.

Arbitrary memory overwrite when VM gets compromised in TX write leading to Memory Corruption.

Information disclosure in DSP Services while loading dynamic module.

Memory Corruption in GPU Subsystem due to arbitrary command execution from GPU in privileged mode.

Memory corruption due to improper access control in kernel while processing a mapping request from root process.

Memory corruption due to double free in Core while mapping HLOS address to the list.

Memory corruption due to use after free in Core when multiple DCI clients register and deregister.

Memory corruption in core due to buffer copy without check9ing the size of input while processing ioctl queries.

information disclosure due to cryptographic issue in Core during RPMB read request.

Memory Corruption in Graphics while accessing a buffer allocated through the graphics pool.

Memory corruption in Graphics while importing a file.

Memory corruption due to double free in core while initializing the encryption key.

Memory corruption due to stack based buffer overflow in core while sending command from USB of large size.

Memory corruption due to improper authentication in Qualcomm IPC while loading unsigned lib in audio PD.

Information Disclosure in Graphics during GPU context switch.

Memory corruption due to improper access control in Qualcomm IPC.

Memory corruption due to stack-based buffer overflow in Core

Information disclosure due to buffer overread in Core

Information disclosure due to buffer overread in Core

Memory corruption in core due to stack-based buffer overflow

Memory corruption in Core due to stack-based buffer overflow.

Memory corruption in video driver due to type confusion error during video playback

Memory corruption in display due to double free while allocating frame buffer memory

Memory corruption in display driver due to incorrect type casting while accessing the fence structure fields

Memory corruption in camera due to improper validation of array index in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer

Memory corruption in diag due to use after free while processing dci packet in Snapdragon Auto, Snapdragon Compute, Snapdragon Con

Memory corruption in graphics due to use-after-free while importing graphics buffer in Snapdragon Auto, Snapdragon Compute, Snapdr

Memory corruption in graphics due to buffer overflow while validating the user address in Snapdragon Auto, Snapdragon Compute, Sna

Memory corruption due to use after free in service while trying to access maps by different threads in Snapdragon Auto, Snapdragon

Information disclosure due to exposure of information while GPU reads the data in Snapdragon Auto, Snapdragon Compute, Snapdragon

Denial of service in BOOT when partition size for a particular partition is requested due to integer overflow when blocks are calc

Possible use after free due to lack of null check of DRM file status after file structure is freed in Snapdragon Auto, Snapdragon

Possible unauthorized access to secure space due to improper check of data allowed while flashing the no access control device con

Possible out of bounds access due to improper input validation during graphics profiling in Snapdragon Auto, Snapdragon Compute, S

Improper validation of input when provisioning the HDCP key can lead to memory corruption in Snapdragon Auto, Snapdragon Compute,

Possible null pointer dereference due to lack of TLB validation for user provided address in Snapdragon Auto, Snapdragon Compute,

Improper access control in TrustZone due to improper error handling while handling the signing key in Snapdragon Auto, Snapdragon

Vulnerabilities
CISA KEV catalog
CWE weaknesses
CAPEC attack patterns
Package vulnerabilities

Threat intelligence
Threat actors
Tools & malware
ATT&CK techniques
IOCs

Detection & defense
Sigma rules
YARA rules
Atomic Red Team tests
D3FEND countermeasures

Compliance
NIST 800-53
ISO 27001:2022
SOC 2 TSC
PCI-DSS v4.0
CIS Controls v8.1

About
All capabilities
Live statistics
Data sources
Privacy policy
Terms of service

threatengine.sh · Open-source threat intelligence platform · 100+ authoritative sources · Every fact traces to its origin