robotics rb5 platform firmware · threatengine.sh

Home/Product/qualcomm robotics rb5 platform firmware

Product

qualcomm robotics rb5 platform firmware

106 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 while using alignments for memory allocation.

Memory Corruption while invoking IOCTL calls when concurrent access to shared buffer occurs.

Memory Corruption when concurrent access to shared buffer occurs due to improper synchronization between assignment and deallocati

Memory Corruption when accessing a buffer after it has been freed while processing IOCTL calls.

Memory Corruption when concurrent access to shared buffer occurs during IOCTL calls.

Memory corruption while handling different IOCTL calls from the user-space simultaneously.

Information disclosure when a weak hashed value is returned to userland code in response to a IOCTL call to obtain a session ID.

Memory corruption while processing shared command buffer packet between camera userspace and kernel.

Memory corruption while handling buffer mapping operations in the cryptographic driver.

Information disclosure while processing a firmware event.

Transient DOS while parsing video packets received from the video firmware.

Memory corruption while handling IOCTL calls to set mode.

Memory corruption while processing MFC channel configuration during music playback.

Memory corruption during video playback when video session open fails with time out error.

Memory corruption while processing a malformed license file during reboot.

Memory corruption during PlayReady APP usecase while processing TA commands.

Transient DOS while parsing the EPTM test control message to get the test pattern.

Cryptographic issue while performing RSA PKCS padding decoding.

Transient DOS while processing an ANQP message.

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.

Transient DOS while processing the EHT operation IE in the received beacon frame.

Transient DOS may occur while parsing SSID in action frames.

Transient DOS while connecting STA to AP and initiating ADD TS request from AP to establish TSpec session.

Cryptographic issue occurs during PIN/password verification using Gatekeeper, where RPMB writes can be dropped on verification fai

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 while processing voice packet with arbitrary data received from ADSP.

Memory corruption while invoking IOCTL calls from the use-space for HGSL memory node.

Memory corruption while handling session errors from firmware.

Cryptographic issue when a controller receives an LMP start encryption command under unexpected conditions.

Transient DOS while parsing probe response and assoc response frame.

Information disclosure while parsing the BSS parameter change count or MLD capabilities fields of the ML IE.

memory corruption when an invalid firehose patch command is invoked.

Cryptographic issue while parsing RSA keys in COBR format.

Memory corruption can occur if VBOs hold outdated or invalid GPU SMMU mappings, especially when the binding and reclaiming of memo

Memory corruption as fence object may still be accessed in timeline destruct after isync fence is released.

Transient DOS while parsing probe response and assoc response frame when received frame length is less than max size of timestamp.

Transient DOS while parsing the BSS parameter change count or MLD capabilities fields of the ML IE.

Transient DOS while parsing the ML IE when a beacon with length field inside the common info of ML IE greater than the ML IE lengt

Memory corruption while creating a fence to wait on timeline events, and simultaneously signal timeline events.

Memory corruption while allocating memory in HGSL driver.

Memory corruption while processing IOCTL call to set metainfo.

Transient DOS while processing TID-to-link mapping IE elements.

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 nei

Transient DOS while parsing ESP IE from beacon/probe response frame.

Transient DOS when driver accesses the ML IE memory and offset value is incremented beyond ML IE length.

Transient DOS while parsing the multiple MBSSID IEs from the beacon, when the tag length is non-zero value but with end of beacon.

Transient DOS while parsing the MBSSID IE from the beacons, when the MBSSID IE length is zero.

Transient DOS while parsing fragments of MBSSID IE from beacon frame.

Memory corruption when the mapped pages in VBO are still mapped after reclaiming by shrinker.

Memory corruption while processing graphics kernel driver request to create DMA fence.

Transient DOS while importing a PKCS#8-encoded RSA key with zero bytes modulus.

Memory corruption when keymaster operation imports a shared key.

Memory corruption while handling user packets during VBO bind operation.

Memory corruption when IOMMU unmap operation fails, the DMA and anon buffers are getting released.

Memory corruption while invoking IOCTL call for GPU memory allocation and size param is greater than expected size.

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

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.

Transient DOS while parse fils IE with length equal to 1.

Memory corruption while validating the TID to Link Mapping action request frame, when a station connects to an access point.

Transient DOS while key unwrapping process, when the given encrypted key is empty or NULL.

Memory corruption when AP includes TID to link mapping IE in the beacons and STA is parsing the beacon TID to link mapping IE.

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 Core while processing control functions.

Memory corruption in Trusted Execution Environment while deinitializing an object used for license validation.

Memory corruption while invoking IOCTLs calls from user space for internal mem MAP and internal mem UNMAP.

Transient DOS while parsing IPv6 extension header when WLAN firmware receives an IPv6 packet that contains IPPROTO_NONE as the n

Memory corruption in Audio when memory map command is executed consecutively in ADSP.

Memory corruption while processing Listen Sound Model client payload buffer when there is a request for Listen Sound session get p

Memory corruption when HLOS allocates the response payload buffer to copy the data received from ADSP in response to AVCS_LOAD_MOD

Transient DOS while parsing ieee80211_parse_mscs_ie in WIN WLAN driver.

Memory corruption while running NPU, when NETWORK_UNLOAD and (NETWORK_UNLOAD or NETWORK_EXECUTE_V2) commands are submitted at the

Memory corruption when resource manager sends the host kernel a reply message with multiple fragments.

Transient DOS when WLAN firmware receives "reassoc response" frame including RIC_DATA element.

Transient DOS while processing a WMI P2P listen start command (0xD00A) sent from host.

Memory corruption while running VK synchronization with KASAN enabled.

Memory corruption in wearables while processing data from AON.

Transient DOS in WLAN Firmware while parsing a BTM request.

Memory corruption in Audio during playback with speaker protection.

Memory corruption in HLOS while running playready use-case.

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

Memory corruption while submitting a large list of sync points in an AUX command to the IOCTL_KGSL_GPU_AUX_COMMAND.

Transient DOS while parsing WPA IES, when it is passed with length more than expected size.

Transient DOS when processing a NULL buffer while parsing WLAN vdev.

Memory corruption when processing cmd parameters while parsing vdev.

Memory corruption in WLAN Host while processing RRM beacon on the AP.

Memory corruption while sending an Assoc Request having BTM Query or BTM Response containing MBO IE.

Transient DOS in Bluetooth Host while rfc slot allocation.

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.

Cryptographic issue in HLOS during key management.

Memory corruption in TZ Secure OS while loading an app ELF.

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

Memory corruption while parsing the ADSP response command.

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

Transient DOS in WLAN Firmware while parsing rsn ies.

Transient DOS in WLAN Firmware while parsing a NAN management frame.

Memory corruption in WLAN Host when the firmware invokes multiple WMI Service Available command.

Improper Access to the VM resource manager can lead to Memory Corruption.

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