dbcve.org
Xmm 7560 FirmwareOperating system · Intel

CVE-2022-26079

HIGH · 8.2 CVSS v3.1 Published 2022-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
Improper conditions check 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 local 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 · high confidence

Improper conditions check in Intel XMM 7560 Modem software allows a privileged local user to escalate privileges. The vulnerability stems from insufficient validation of certain conditions in the privilege check logic, enabling a user with existing elevated privileges to gain additional unauthorized access.

MitigationUpdate Intel XMM 7560 Modem software to version M2_7560_R_01.2146.00 or later. For embedded systems or devices using this modem, obtain and deploy the vendor-supplied firmware update through appropriate change management processes.

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
Xmm 7560 FirmwareOperating system
Affected:< m2_7560_r_01.2146.00

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

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

  1. Identify Intel XMM 7560 modem presence
    Check device specifications, hardware inventory, or system logs for Intel XMM 7560 modem. On Linux, run 'lsusb' or check 'dmesg' for 'XMM 7560' or 'Intel' modem strings. On embedded devices, consult the vendor hardware documentation.
    Affected if The device or system contains an Intel XMM 7560 modem module
  2. Retrieve modem firmware version
    Access the modem through AT command interface. Common methods: 1) Use serial/USB AT terminal, send 'ATI' or 'AT+CGMR' command. 2) On Android devices, check under Settings > About Phone > SIM Status or modem logs. 3) On IoT/embedded devices, query modem via vendor-specific API or management interface.
    Affected if Unable to retrieve firmware version indicates limited visibility but does not confirm safety
  3. Compare firmware version against vulnerable range
    Parse the firmware version string obtained (e.g., from 'ATI' response). Compare numerically against 'm2_7560_r_01.2146.00'. Versions below this threshold (e.g., m2_7560_r_01.2145.XX, m2_7560_r_01.2XXX) are vulnerable.
    Affected if Firmware version string is lower than m2_7560_r_01.2146.00 (e.g., 01.2145.00, 01.2100.00, etc.)
  4. Verify privilege escalation attack surface
    This vulnerability requires a 'privileged local user' who already has elevated access on the host system. Audit local user accounts, sudo permissions, and any processes with elevated privileges that could interact with the modem interface.
    Affected if Systems where untrusted local users have any level of elevated access to modem configuration interfaces

Your environment is affected if it contains an Intel XMM 7560 modem with firmware version below m2_7560_r_01.2146.00 and allows local privileged users to interact with the modem.

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

Update Intel XMM 7560 Modem software to version M2_7560_R_01.2146.00 or later. For embedded systems or devices using this modem, obtain and deploy the vendor-supplied firmware update through appropriate change management processes.

Recommended fix High confidence

M2_7560_R_01.2146.00

  1. Obtain the Intel XMM 7560 Modem firmware version M2_7560_R_01.2146.00 or later from the official Intel support channels
  2. Follow Intel's standard firmware update procedure for the XMM 7560 modem device
  3. Verify the firmware has been successfully applied by checking the modem firmware version

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

Fix this in Xmm 7560 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26079 — 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-26079 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