CVE-2022-27639
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 · uneditedIncomplete cleanup in some Intel(R) XMM(TM) 7560 Modem software before version M2_7560_R_01.2146.00 may allow a privileged user to potentially enable escalation of privilege via adjacent access.
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 confidenceIncomplete cleanup in Intel XMM 7560 Modem software before version M2_7560_R_01.2146.00 may allow a privileged user to potentially escalate privileges via adjacent network access. The vulnerability stems from insufficient sanitization or cleanup routines that could be exploited by an attacker with local/network proximity to the modem.
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< m2_7560_r_01.2146.00CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/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 Intel XMM 7560 modem presenceInventory network devices or modem components to determine if an Intel XMM 7560 modem is deployed in the environment. Consult device inventories, network topology documentation, or query modem management interfaces.Affected if The environment contains an Intel XMM 7560 modem device.
-
Retrieve the modem firmware versionAccess the modem management interface, diagnostic logs, or device configuration to obtain the current firmware version string. This is typically found in modem status pages, AT command outputs, or firmware metadata.Affected if Unable to retrieve a firmware version for the modem.
-
Compare firmware version against the affected rangeParse the retrieved firmware version and compare it lexicographically to the threshold version m2_7560_r_01.2146.00. Ensure proper version string formatting is understood (e.g., comparing m2_7560_r_01.2145.00 vs m2_7560_r_01.2146.00).Affected if The installed firmware version is lower than m2_7560_r_01.2146.00 (e.g., m2_7560_r_01.2145.00 or earlier).
The user is affected if an Intel XMM 7560 modem with firmware version earlier than m2_7560_r_01.2146.00 is present in their environment.
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.
dbcve · scopedUpdate Intel XMM 7560 Modem software to version M2_7560_R_01.2146.00 or later to address the incomplete cleanup vulnerability. Restrict physical and adjacent network access to modem infrastructure as a compensating control.
M2_7560_R_01.2146.00
- Identify the current Intel XMM 7560 modem firmware version by accessing the modem's administrative interface or using AT commands (e.g., AT+CGMR or ATI)
- Navigate to Intel's official support website and locate the download page for XMM 7560 modem firmware
- Download the fixed firmware version M2_7560_R_01.2146.00 or later
- Review Intel's firmware update documentation specific to the XMM 7560 modem
- Apply the firmware update following Intel's standard procedures (this typically involves uploading the firmware file through the modem's management interface)
- After updating, verify the new firmware version is M2_7560_R_01.2146.00 or later using AT commands
- Confirm the vulnerability is resolved by verifying the modem operates normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27639 — 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-27639 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