CVE-2022-33230
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 in FM Host due to buffer copy without checking the size of input in FM Host
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 confidenceA buffer overflow vulnerability in FM Host where data is copied into a fixed-size buffer without validating the input size, allowing memory corruption that could lead to code execution or denial of service.
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 if Qualcomm FM firmware is presentCheck system firmware or hardware specifications for one of these chips: Aqt1000, Wcn3991, Wcn3998, Qca6420, Qca6430, Qca6554a, Qca6564au, or Qca6574. This may be listed in device documentation, system info commands, or firmware version outputs.Affected if Any of the listed Qualcomm firmware components are present on the device
-
Determine if FM Host feature is enabledCheck device configuration or running services for FM Host daemon or FM radio host process. On Linux systems, this may appear in process lists (ps aux) or service listings (systemctl list-units). Look for processes named 'fm_host', 'fmradio', or similar FM-related services.Affected if FM Host or FM radio host service is actively running or enabled on the device
-
Verify FM radio functionality is in useCheck if any application or service is actively using the FM receiver/transmitter subsystem. This may be observable through active FM-related log entries, open file handles to FM devices (/dev/fm* or similar), or FM-related network activity if remote FM control is enabled.Affected if FM radio subsystem is actively accessed or configured on the system
If the device contains any of the listed Qualcomm firmware variants (Aqt1000, Wcn3991, Wcn3998, Qca6420, Qca6430, Qca6554a, Qca6564au, Qca6574) and has FM Host feature enabled or in use, the environment is affected by this buffer overflow 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 bounds checking on all buffer copy operations in FM Host; validate input lengths before memory copy functions and ensure buffers are appropriately sized.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33230 — 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-2022-33230 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