CVE-2025-27034
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 selecting the PLMN from SOR failed list.
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 occurs during the selection of a PLMN (Public Land Mobile Network) from a list of failed SOR (likely Service-Oriented Routing) entries. This is a critical memory safety vulnerability in telecom network selection logic.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 wireless firmware componentsExamine system firmware, kernel modules, or device firmware binaries for references to Fastconnect 6900, Fastconnect 7800, Qca6174a, Qca6391, Qca6574a, Qca6584au, Qca6595au, or Qca6696. On Linux systems, check 'lspci -v' or 'rfkill list' for wireless adapters, or review /lib/firmware/ for qca*.fw files.Affected if Any of the listed Qualcomm firmware identifiers appear in system components or firmware dumps
-
Verify wireless chipset vendor and modelRun 'lspci | grep -i network' or 'lspci | grep -i wireless' to list wireless devices. For USB wireless adapters, use 'lsusb'. Check the chipset manufacturer and model number against the affected product list.Affected if The device uses a Qualcomm Fastconnect or Qca-series wireless chipset from the affected list
-
Check firmware version stringsIf a Qualcomm wireless device is identified, query its firmware version through vendor-specific tools (e.g., 'ethtool -i', 'iw dev', or manufacturer diagnostic utilities). Compare the firmware version against the affected products.Affected if The firmware version corresponds to any of the listed Qualcomm Fastconnect or Qca product lines regardless of version number (all versions affected)
-
Review network selection configurationExamine system logs or configuration files for PLMN (Public Land Mobile Network) selection activity and SOR (Service-Oriented Routing) entries, particularly in cellular or telecom-related processes. Look for logs containing 'PLMN', 'SOR', or 'network selection'.Affected if The system performs PLMN or network selection operations using the affected Qualcomm firmware components
A system is affected if it contains any Qualcomm Fastconnect or Qca-series wireless firmware from the listed product families, regardless of version, since all versions of these products are vulnerable to the memory corruption flaw in PLMN selection from failed SOR entries.
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 dataApply vendor-provided patches immediately as they become available. Given the critical severity (CVSS 9.8) and telecom network context, prioritize patching any affected radio access network or core network equipment.
- 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-27034 — 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-27034 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