dbcve.org
315 5g Iot Modem FirmwareOperating system · Qualcomm

CVE-2025-27054

HIGH · 7.8 CVSS v3.1 Published 2025-10-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Memory corruption while processing a malformed license file during reboot.

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 confidence

Memory corruption vulnerability in license file parsing during the reboot process. The application fails to properly validate or handle a malformed license file, leading to memory corruption that can be exploited during the reboot sequence.

MitigationImplement strict validation of license file structure and contents before processing; ensure bounds checking and memory safety in license parsing routines; apply vendor patches when available.

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 data
315 5g Iot Modem FirmwareOperating system
Affected:all versions
9205 Lte Modem FirmwareOperating system
Affected:all versions
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8031 FirmwareOperating system
Affected:all versions
Ar8035 FirmwareOperating system
Affected:all versions
Sa8770p FirmwareOperating system
Affected:all versions
Sa8775p FirmwareOperating system
Affected:all versions
Sa9000p FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Qualcomm firmware product
    Check system information or firmware version by running 'at+qver' or checking the modem firmware identification (e.g., for Qualcomm 315 5g IoT Modem, Qualcomm 9205 LTE Modem, Aqt1000, Ar8031, Ar8035, Sa8770p, Sa8775p, or Sa9000p)
    Affected if The system is running any of the listed affected Qualcomm firmware products (315 5g IoT Modem, 9205 LTE Modem, Aqt1000, Ar8031, Ar8035, Sa8770p, Sa8775p, or Sa9000p)
  2. Verify license file parsing is enabled
    Check the modem or device configuration for license file loading/enable flags. Look for configuration entries such as 'license_file_enable', 'license_parsing', or similar settings in the firmware configuration or startup scripts
    Affected if License file parsing is enabled in the device configuration or startup parameters
  3. Locate license files on the system
    Search for license files in typical locations such as /etc/license/, /opt/license/, or vendor-specific paths. Use commands like 'find / -name *license*' or check the vendor documentation for license file storage locations
    Affected if License files are present on the system in any configuration directory
  4. Inspect the reboot process configuration
    Review the reboot sequence or startup scripts for license file loading. Check init scripts, rc boot scripts, or vendor-specific reboot handlers that process license files during system restart
    Affected if The reboot process includes steps to load or validate license files
  5. Check for license validation mechanisms
    Examine whether the system performs any validation on license file structure before parsing. Look for license file format checks, integrity verification, or schema validation in the boot logs or configuration
    Affected if No explicit license file structure validation or integrity checks are performed before parsing the license file during reboot

The system is affected if it runs any of the listed Qualcomm firmware products (315 5g IoT, 9205 LTE, Aqt1000, Ar8031, Ar8035, Sa8770p, Sa8775p, Sa9000p) with license file parsing enabled and license files present in the reboot sequence.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict validation of license file structure and contents before processing; ensure bounds checking and memory safety in license parsing routines; apply vendor patches when available.

Fix this in 315 5g Iot Modem Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27054 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27054 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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