CVE-2021-30348
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 · uneditedImproper validation of LLM utility timers availability can lead to denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music
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 confidenceImproper validation of LLM (Low Latency Module) utility timers availability in Snapdragon chips can lead to denial of service. The vulnerability stems from the system not properly checking timer availability before use, causing a DoS condition when timers are unavailable.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the Snapdragon chip model in your deviceCheck device specifications, system information, or hardware documentation to determine the exact Qualcomm Snapdragon model number (e.g., Pq8009, Apq8017, Apq8064au, Apq8096au, Aqt1000, Ar8031, Ar8035, Csra6620)Affected if The device uses any of the following models: Pq8009, Apq8017, Apq8064au, Apq8096au, Aqt1000, Ar8031, Ar8035, or Csra6620
-
Confirm LLM (Low Latency Module) functionality is in useDetermine if the device or application utilizes the Low Latency Module feature of the Snapdragon chip. This may be documented in product specifications or embedded system design documentation.Affected if The device leverages LLM timers for time-sensitive operations
-
Monitor for timer-related failures or unexpected system resetsReview system logs, kernel logs, or embedded system event logs for patterns indicating timer unavailability errors, failed timer initialization, or correlated system resets. Check for error messages mentioning timer availability or LLM utility failures.Affected if Logs show repeated timer initialization failures, timer availability check errors, or unexplained system resets occurring during timer-dependent operations
-
Check firmware version if accessibleIf you have access to the device firmware (via debug interface, bootloader, or manufacturer tools), retrieve the current firmware version string for the Snapdragon chipAffected if The firmware version corresponds to any of the affected products listed (all versions of Pq8009, Apq8017, Apq8064au, Apq8096au, Aqt1000, Ar8031, Ar8035, Csra6620 are affected)
Your environment is affected if your device uses a listed Snapdragon model (Pq8009, Apq8017, Apq8064au, Apq8096au, Aqt1000, Ar8031, Ar8035, or Csra6620) and utilizes LLM timer functionality, since all firmware versions of these products lack proper timer availability validation.
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-supplied firmware updates from Qualcomm for affected Snapdragon products. Until patches are available, monitor for unexpected timer failures and system resets.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30348 — 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-2021-30348 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