CVE-2025-27044
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMemory corruption while executing timestamp video decode command with large input values.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMemory corruption vulnerability in video decode timestamp handling where large input values are not properly validated, allowing an attacker to trigger out-of-bounds memory access during video decoding operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Qualcomm Fastconnect firmware usageCheck system or device inventory for devices using Qualcomm Fastconnect 6900 or 7800 WiFi/Bluetooth chipsets. On Linux, this may appear in lspci, lsusb, or kernel module outputs. Review hardware manifests or firmware databases for your managed endpoints.Affected if Any endpoint contains Qualcomm Fastconnect 6900 or 7800 firmware
-
Identify Qualcomm mobile platform firmware usageCheck for devices using Qualcomm Sc8380xp processors or chipsets. Review device specifications, firmwareSBOMs, or hardware asset lists for systems with this Qualcomm platform.Affected if Any endpoint contains Qualcomm Sc8380xp firmware
-
Identify Qualcomm audio codec firmware usageCheck for devices with Qualcomm Wcd9380, Wcd9385, Wsa8840, Wsa8845, or Wsa8845h audio codec firmware. These are typically found in smartphones, tablets, or audio subsystems. Query device firmware listings or audio driver information.Affected if Any endpoint contains Qualcomm Wcd9380, Wcd9385, Wsa8840, Wsa8845, or Wsa8845h firmware
-
Verify video decode functionality is in useConfirm that video decoding operations are performed on affected devices. Check if video playback, streaming, or video conferencing applications are active. Review process lists or system activity logs for video decode activity.Affected if Video decode operations are performed on devices with affected firmware components
-
Check for timestamp input validation in video pipelineIf you have access to firmware or driver source code, search for video decode timestamp handling functions. Look for code paths that process timestamp values without proper bounds checking before memory allocation. This typically requires access to the firmware binary or debug symbols.Affected if Timestamp values from external input are processed without strict bounds validation before memory operations
If your environment contains any devices with Qualcomm Fastconnect 6900/7800, Sc8380xp, Wcd9380/9385, or Wsa8840/8845/8845h firmware and those devices perform video decoding, the environment is affected.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict bounds checking on timestamp values before passing to the video decode command; validate that input sizes fall within expected memory allocation limits.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27044 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27044 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data