CVE-2025-47394: High Severity Vulnerability in platform/vendor/qcom/opensource/dsp-kernel

Summary

01/03/2026
Yes i
High
Not published

CVE-2025-47394: ... Affects platform/vendor/qcom/opensource/dsp-kernel versions >= SoCVersion:0, < SoCVersion:2026-03-05. Fixed in SoCVersion:2026-03-05. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The platform/vendor/qcom/opensource/dsp-kernel package is a critical component of the Android ecosystem, providing essential functionalities for digital signal processing. This package is utilized in various Qualcomm System on Chips (SoCs) and is integral to the performance and efficiency of Android devices. However, it has been identified to contain a vulnerability that could potentially be exploited, leading to severe consequences for device security and stability.

Vulnerability Detail

The vulnerability identified as CVE-2025-47394 originates from a flaw in the dsp-kernel's handling of certain operations within the fastrpc.c file. This issue could allow an attacker to manipulate memory allocations, leading to potential crashes or unauthorized access to sensitive data. The severity of this vulnerability is classified as high, indicating that it poses a significant risk to affected systems, particularly those utilizing the vulnerable SoC versions.

How To Fix

Minimum fixed version

SoCVersion:2026-03-05

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary measure, users are advised to limit access to the affected components of the dsp-kernel until the patch can be applied. This may involve disabling certain functionalities that rely on the vulnerable code in fastrpc.c.

Conclusion

In summary, CVE-2025-47394 represents a significant security risk within the platform/vendor/qcom/opensource/dsp-kernel package. Users are strongly encouraged to update to the patched version to mitigate potential threats. For those unable to update immediately, implementing temporary workarounds is advisable.

See every vulnerability recorded for platform/vendor/qcom/opensource/dsp-kernel →

Share this vulnerability

FAQ

CVE-2025-47394 is a high severity vulnerability found in the platform/vendor/qcom/opensource/dsp-kernel package, which could allow attackers to exploit memory handling issues.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The risks include potential crashes, unauthorized access to sensitive data, and overall instability of the affected devices.

Yes, a patch is available and can be applied by updating to the version released on March 5, 2026.

If you cannot apply the patch immediately, it is recommended to limit access to the affected components as a temporary workaround.

How To Fix

Minimum fixed version

SoCVersion:2026-03-05

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback