CVE-2025-20722
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 · uneditedIn gnss driver, there is a possible out of bounds read due to an integer overflow. This could lead to local information disclosure if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS09920036; Issue ID: MSV-3798.
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 confidenceIn the gnss driver, an integer overflow can cause an out of bounds read, leading to local information disclosure. Exploitation requires the attacker to already have System-level privileges, with no user interaction needed.
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= 2024q1= 14.0= 15.0= 21.02.0= 23.05CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 the product and firmware versionCheck the system information or firmware version using the vendor-specific command (e.g., `cat /etc/version`, `getprop ro.build.version.release` for Android, or check the RDK/OpenWrt system settings)Affected if The product is RDK B version 2024q1, Android 14.0 or 15.0, or OpenWRT 21.02.0 or 23.05
-
Determine if the gnss driver is presentCheck for the gnss driver module or service on the system. On Android, examine `/system/lib64/` or `/vendor/lib64/` for gnss-related libraries (e.g., `gnss.default.so`). On OpenWRT or RDK, check `/lib/modules/` for gnss kernel modules or look for gnss-related processes via `ps`Affected if The gnss driver or gnss-related library is installed on the system
-
Verify gnss functionality is enabledCheck if the gnss service is running or if the gnss HAL (Hardware Abstraction Layer) is enabled. On Android, use `getprop | grep gnss` or check `/vendor/etc/` for gnss configuration. On embedded devices, examine `/etc/config/` or system configuration files for gnss settingsAffected if The gnss driver is actively enabled or the gnss service is running on the device
-
Check current privilege levelDetermine if the process or user has System-level privileges by examining the running processes or user context. Use commands like `whoami`, `id`, or examine process permissions with `ps -o user,pid,comm`Affected if The attacker already possesses System-level privileges (this is a prerequisite for exploitation)
A user is affected if they are running any of the specific affected versions (RDK B 2024q1, Android 14.0/15.0, or OpenWRT 21.02.0/23.05) AND the gnss driver is present and enabled on their system.
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 patch ALPS09920036 when available. Until then, enforce strict access controls to prevent attackers from attaining System privilege, as this is a prerequisite for exploiting the vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20722 — 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-20722 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