dbcve.org
Xmm 7560 FirmwareOperating system · Intel

CVE-2022-26367

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 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 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 buffer restrictions in Intel XMM 7560 Modem software allow a privileged local user to escalate privileges. The vulnerability stems from insufficient bounds checking in the modem firmware, enabling a privileged attacker to potentially execute code at elevated privilege levels.

MitigationUpdate Intel XMM 7560 Modem software to version M2_7560_R_01.2146.00 or later to obtain the vendor patch for proper buffer restriction controls.

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
    Use system diagnostic tools or modem management utilities to list installed modem devices. Look for XMM 7560 or Intel modem entries in device inventories, dmesg logs, or modem manager outputs.
    Affected if The system does not contain an Intel XMM 7560 modem - no further action needed.
  2. Query modem firmware version
    Execute AT command queries appropriate for Intel modems (such as AT+CGMR or vendor-specific version commands) through a serial interface, modem diagnostic tool, or modem manager API to retrieve the installed firmware build string.
    Affected if Unable to retrieve a firmware version string from the modem.
  3. Compare firmware version against the fixed release
    Extract the numeric build identifier from the firmware version string (the format is m2_7560_r_XX.XXXX.XX). Compare this build number to 01.2146.00 using standard version comparison logic, treating earlier builds as vulnerable.
    Affected if The installed firmware version is earlier than m2_7560_r_01.2146.00 (for example, m2_7560_r_01.2000.00 would be vulnerable).
  4. Verify user privilege context
    Determine if the account being assessed has privileged local access on the host system, as the vulnerability requires a privileged local user to trigger the insufficient bounds checking in the modem firmware.
    Affected if The user has privileged (administrator/root) local access and the firmware version is below m2_7560_r_01.2146.00.

A system is affected if it contains an Intel XMM 7560 modem running firmware versions earlier than m2_7560_r_01.2146.00 and the user possesses privileged local access to the system.

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 to obtain the vendor patch for proper buffer restriction controls.

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. Apply the firmware update to the Intel XMM 7560 Modem following the standard Intel firmware upgrade procedure for your specific device/platform
  3. Verify the installed firmware version is M2_7560_R_01.2146.00 or later after the update completes

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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