CVE-2025-21465
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 · uneditedInformation disclosure while processing the hash segment in an MBN file.
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 confidenceAn information disclosure vulnerability exists in the parsing of the hash segment within MBN (Modem Binary) files. MBN files are Qualcomm firmware boot images used in mobile devices. The vulnerability allows a local or potentially remote attacker to access sensitive information during the hash processing routine.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
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 installed Qualcomm modem firmware versionCheck the system or device for Qualcomm modem firmware version information. Common methods: check /proc/version, AT command responses (AT+CGMR or ATI), or device system info. For IoT devices, check the modem module firmware via manufacturer APIs or diagnostic tools.Affected if The firmware version matches any of the affected products: Qualcomm 315 5G IoT, 9205 LTE, Aqt1000, Ar8031, Ar8035, Qcm2290, Qcm4290, or Qcm4325 (all versions are affected).
-
Determine if MBN file processing is enabledSearch for MBN-related tools, parsers, or libraries on the system. Look for files containing 'mbn' in the name (e.g., mbparse, mbntool, libmbn). Check for processes or services that handle firmware update files with .mbn extension.Affected if MBN parsing utilities or firmware update tools are present and active on the system.
-
Check for active MBN hash processing routinesMonitor or inspect running processes for any that perform hash validation or processing on MBN firmware files. Check logs for entries related to MBN hash verification, firmware loading, or modem initialization.Affected if Any process is actively parsing or processing hash segments within MBN files.
-
Inspect network exposure of MBN processing servicesReview network listening services and APIs that accept firmware files. Check if there are any web interfaces, diagnostic ports, or remote management services that accept MBN file uploads or parse modem firmware.Affected if Services exist that accept or process MBN files from network sources, especially untrusted inputs.
A system is affected if it runs any of the listed Qualcomm modem firmware versions (all versions) AND actively processes MBN files, particularly through services that handle the hash segment during firmware parsing.
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 or firmware updates for products that process MBN files. Restrict processing of untrusted MBN files to sandboxed environments and validate file sources before processing.
- Consultation2.0 h
- Implementation1.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21465 — 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-21465 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