CVE-2025-47363
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 when calculating oversized partition sizes without proper checks.
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 occurs when the system calculates partition sizes without proper validation, allowing oversized partition sizes to be processed. This can lead to buffer overflows or improper memory allocation, potentially allowing an attacker to overwrite memory boundaries and execute arbitrary code.
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 firmware versionCheck the system firmware version by querying the bootloader, /proc/version, or device information interface (e.g., 'cat /proc/version', '固件版本' in system settings, or via UART/serial console at boot)Affected if The firmware version string matches any of: Qam8255p, Qam8295p, Qam8620p, Qam8650p, Qam8775p, Qamsrv1h, Qamsrv1m, Qca6574au (all versions are affected)
-
Confirm hardware modelCheck the hardware or board identifier via 'cat /sys/class/hwmon/*/name', 'cat /proc/device-tree/model', or physical board labelingAffected if The hardware model corresponds to one of the affected firmware variants listed above
-
Locate partition serviceIdentify if the partition management service is running by checking running processes (ps command) for components named 'qamsrv', 'partition', 'partitionmgr', or check /system/bin or /vendor/bin for relevant binariesAffected if A partition management service or binary named qamsrv, partitiond, or similar is present and active on the system
-
Inspect partition configurationExamine partition table definitions in /proc/partition, /etc/fstab, /dev/block/, or device tree overlays (DTB) for any partition entriesAffected if Partition configuration files exist and the system defines multiple partitions, indicating the vulnerable calculation logic is invoked
-
Check for partition size anomaliesReview system logs (dmesg, logcat, /var/log/) for warnings related to partition size, memory allocation failures, or buffer overflow indicators near partition initializationAffected if Logs contain errors such as 'partition size too large', 'allocation failed', or memory corruption warnings during boot or partition operations
You are affected if your device runs any of the listed Qualcomm firmware variants (Qam8255p, Qam8295p, Qam8620p, Qam8650p, Qam8775p, Qamsrv1h, Qamsrv1m, Qca6574au) as all versions contain the vulnerability.
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 rigorous input validation and bounds checking on all partition size calculations to ensure values remain within safe limits before memory allocation.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2025-47363 — 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-47363 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