dbcve.org
Apq8096au FirmwareOperating system · Qualcomm

CVE-2022-22063

HIGH · 7.8 CVSS v3.1 Published 2022-12-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Memory corruption in Core due to improper configuration in boot remapper.

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 confidence

Memory corruption vulnerability in the Core component stemming from improper configuration of the boot remapper. The boot remapper appears to mishandle memory mapping during the boot process, leading to memory corruption that could potentially allow privilege escalation or code execution.

MitigationApply relevant security patches from Microsoft; ensure boot configuration integrity and verify secure boot settings are properly implemented.

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
Apq8096au FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9645 FirmwareOperating system
Affected:all versions
Qca6174 FirmwareOperating system
Affected:all versions
Qca6174a FirmwareOperating system
Affected:all versions
Qca6574a FirmwareOperating system
Affected:all versions
Qca6574au FirmwareOperating system
Affected:all versions
Wcn3990 FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Qualcomm chip model in your device
    Check device documentation, system information, or use commands like 'lspci', 'lsusb', or check /proc/cpuinfo for hardware identifiers. Look for model numbers: Apq8096au, Mdm9640, Mdm9645, Qca6174, Qca6174a, Qca6574a, Qca6574au, or Wcn3990.
    Affected if The device uses any of the listed Qualcomm chip models (Apq8096au, Mdm9640, Mdm9645, Qca6174, Qca6174a, Qca6574a, Qca6574au, Wcn3990)
  2. Check the firmware version
    Retrieve the firmware version from the device. This may require accessing boot logs, firmware management interfaces, or vendor-specific tools. For example, check dmesg for firmware loading messages, or use vendor-provided firmware version queries.
    Affected if The device is running firmware from any of the affected product lines (all versions of the listed Qualcomm firmware products are affected)
  3. Verify boot remapper configuration
    Examine boot configuration files, boot logs, or memory mapping settings. Check if custom or non-standard boot remapper configurations are in place. Look for boot parameters related to memory mapping in bootloader configurations (e.g., UEFI settings, boot.ini, or vendor-specific boot loaders).
    Affected if A custom or non-standard boot remapper configuration is present that could trigger the memory mapping mishandling during boot
  4. Check for evidence of memory corruption
    Review system logs (dmesg, boot logs, kernel logs) for signs of memory corruption, boot failures, or unexpected memory access errors occurring during or shortly after boot. Look for error patterns like 'memory corruption', 'invalid memory map', or 'boot remap' related errors.
    Affected if Memory corruption errors or abnormal boot-time memory mapping errors are present in logs

If your device uses any of the affected Qualcomm firmware products (Apq8096au, Mdm9640, Mdm9645, Qca6174, Qca6174a, Qca6574a, Qca6574au, Wcn3990), you are affected since all versions of these products contain the vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply relevant security patches from Microsoft; ensure boot configuration integrity and verify secure boot settings are properly implemented.

Recommended fix Moderate confidence

Obtain the fixed firmware release from Qualcomm through your device OEM; specific version numbers are available in Qualcomm's security advisory

  1. Contact your device manufacturer (OEM) to request the CVE-2022-22063 firmware update for your specific device model
  2. Verify with Qualcomm's official security advisory on www.qualcomm.com for the fixed firmware version applicable to your chipset
  3. Apply the OEM-provided firmware update through the device's standard update mechanism
  4. After updating, verify the patch level matches the version specified in Qualcomm's security bulletin
Caveat Firmware updates may require device reboot; some older devices may not receive updates if end-of-life

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Apq8096au Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22063 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22063 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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