CVE-2022-42498
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 Pixel cellular firmware, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-240662453References: N/A
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 confidenceOut-of-bounds write vulnerability in Pixel cellular (baseband/modem) firmware due to a missing bounds check. This allows remote code execution with no required privileges or user interaction, making it highly exploitable.
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 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm device typeIdentify if the target device is a Google Pixel phone or other Android device with cellular baseband/modem firmware. Use 'Settings > About Phone' or check /sys/class/boot_info for device model.Affected if Device is a Google Pixel or Android phone with baseband/modem hardware and all Android versions are affected
-
Verify baseband module is presentCheck for baseband/modem firmware presence by examining /proc/version, /sys/class/boeffla-wl, or using 'getprop' commands like 'getprop ro.baseband' or 'getprop gsm.version.baseband'.Affected if Baseband/modem firmware is present on the device (which is the case for most Android phones)
-
Check cellular connectivity is enabledConfirm the device has cellular radio enabled. Check via 'Settings > Network & Internet > SIM cards' or run 'settings get global mobile_data' or check /sys/class/net/ for cellular interfaces like rmnet0, ccmni0.Affected if Cellular radio and baseband firmware are actively in use on the device
-
Confirm Android versionRun 'getprop ro.build.version.release' or check 'Settings > About Phone > Android version'. All Android versions are affected per the CVE.Affected if Device runs any version of Android - all versions are within scope
If the device is any Google Pixel or Android phone with active cellular/baseband firmware, it is affected by this 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 dataApply vendor firmware updates from Google/Pixel as they become available; until then, consider network segmentation to limit exposure of affected devices.
- Consultation8.0 h
- Implementation2.0 h
- Testing16.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 $8,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42498 — 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-42498 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