CVE-2024-45548

Memory corruption while processing FIPS encryption or decryption validation functionality IOCTL call...

CVE-2024-45546

Memory corruption while processing FIPS encryption or decryption IOCTL call invoked from user-space...

CVE-2024-33021

Memory corruption while processing IOCTL call to set metainfo...

CVE-2024-22346

Db2 for IBM i 7.2, 7.3, 7.4, and 7.5 infrastructure could allow a local user to gain elevated privileges due to an unqualified library call. A malicious actor could cause user-controlled code to run with administrator privilege. IBM X-Force ID: 280203...

CVE-2024-53730

Cross-Site Request Forgery CSRF vulnerability in springthistle April's Call Posts aprils-call-posts allows Stored XSS.This issue affects April's Call Posts: from n/a through = 2.1.1...

PT-2025-13180

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The issue concerns the OP-TEE supplicant, a user-space daemon in the Linux kernel, which can become hung, crashed, or killed during an OP-TEE RPC call. This can lead to a system hang-up...

MAL-2025-1042 Malicious code in lib-automotive-call-cdm (npm)

The package communicates with a domain associated with malicious activity...

Malicious code in lib-automotive-call-cdm (npm)

The package communicates with a domain associated with malicious activity...

CVE-2024-45584

Memory corruption can occur when a compat IOCTL call is followed by a normal IOCTL call from userspace...

CVE-2024-45584

CVE-2024-45584 involves memory corruption in Qualcomm chipsets caused by a sequence: a compat IOCTL call followed by a normal IOCTL call from userspace. The vulnerability arises from the call order, potentially allowing memory corruption with local access. Public descriptions consistently state t...

CVE-2024-45584 Untrusted Pointer Dereference in Automotive Android OS

Memory corruption can occur when a compat IOCTL call is followed by a normal IOCTL call from userspace...

CVE-2024-45561 Use After Free in Windows WLAN Host

Memory corruption while handling IOCTL call from user-space to set latency level...

CVE-2024-45561

CVE-2024-45561 corresponds to a memory corruption issue observed when handling an IOCTL call from user-space to set latency level on Qualcomm chipsets. Affected component/behavior: IOCTL latency-level handling in kernel/user-space interface; root cause described as memory corruption. Impact as st...

CVE-2024-38404 Buffer Over-read in Multi Mode Call Processor

Transient DOS when registration accept OTA is received with incorrect ciphering key data IE in modem...

CVE-2024-38404 Buffer Over-read in Multi Mode Call Processor

Transient DOS when registration accept OTA is received with incorrect ciphering key data IE in modem...

CVE-2024-38404

CVE-2024-38404 describes a transient DoS in Qualcomm modem components triggered when a registration-accept OTA contains incorrect ciphering key data. The issue is documented across multiple feeds (NVD/NCSC/Red Hat summaries) with the same description. Connected sources indicate impact on Qualcomm...

Malicious code in @sn4k-s3c/call-home (npm)

--- -= Per source details. Do not edit below this line.=-...

CVE-2024-36437: Improper Export of Android Application Components

The com.enflick.android.TextNow aka TextNow: Call + Text Unlimited application 24.17.0.2 for Android enables any installed application with no permissions to place phone calls without user interaction by sending a crafted intent via the com.enflick.android.TextNow.activities.DialerActivity...

CVE-2024-36437

The com.enflick.android.TextNow aka TextNow: Call + Text Unlimited application 24.17.0.2 for Android enables any installed application with no permissions to place phone calls without user interaction by sending a crafted intent via the com.enflick.android.TextNow.activities.DialerActivity...

PT-2025-2716 · Qualcomm · Snapdragon +108

Name of the Vulnerable Software and Affected Versions: No specific software or versions are mentioned in the provided descriptions. Description: Memory corruption can occur when a compat IOCTL call is followed by a normal IOCTL call from userspace. This issue arises due to the sequence of these...