dbcve.org
Xmm 7560 FirmwareOperating system · Intel

CVE-2022-26045

HIGH · 7.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 →
74/100
Remediation priority · Elevated
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 buffer restrictions 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 physical 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 confidence

Improper buffer restrictions in Intel XMM 7560 Modem software before version M2_7560_R_01.2146.00 allow a privileged user with physical access to potentially execute code and escalate privileges. The vulnerability stems from inadequate bounds checking on buffers in the modem firmware, which could be exploited through physical access to the device.

MitigationApply Intel XMM 7560 Modem software version M2_7560_R_01.2146.00 or later to remediate. Limit physical access to affected devices and ensure only trusted privileged users have access.

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

CVSS:3.1/AV:P/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
    Query system hardware information or modem inventory logs to confirm an Intel XMM 7560 modem is installed in the device
    Affected if The device does not have an Intel XMM 7560 modem installed, then it is not affected
  2. Retrieve modem firmware version
    Use AT command interface (for example, ATI or AT+CGMR) or vendor management tools to query the installed firmware version of the Intel XMM 7560 modem
    Affected if Unable to retrieve firmware version from the modem
  3. Compare firmware version against vulnerable range
    Compare the retrieved firmware version string to M2_7560_R_01.2146.00 using version comparison. Versions below this threshold (for example, M2_7560_R_01.2145.00 or earlier) are vulnerable
    Affected if The installed firmware version is less than M2_7560_R_01.2146.00 (for example, m2_7560_r_01.2145.00, m2_7560_r_01.2100.00, or any version starting with a lower release number in the 01.2xxx range)
  4. Verify attack surface conditions
    Assess whether the device with the vulnerable modem firmware is accessible to untrusted physical actors or whether untrusted privileged accounts exist on the system that could interact with the modem interface
    Affected if The vulnerable firmware version is present AND the device has physical accessibility to untrusted users OR untrusted privileged accounts can access the modem

A device is affected if it contains an Intel XMM 7560 modem running firmware version lower than M2_7560_R_01.2146.00 and physical or privileged access to the modem is possible.

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 Intel XMM 7560 Modem software version M2_7560_R_01.2146.00 or later to remediate. Limit physical access to affected devices and ensure only trusted privileged users have access.

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 Intel's official support channels
  2. Follow the standard Intel firmware update procedure for the XMM 7560 Modem device
  3. Verify the firmware has been successfully applied by checking the modem software 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 / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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