dbcve.org
Xmm 7560 FirmwareOperating system · Intel

CVE-2022-26369

HIGH · 8.1 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 →
83/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
Out-of-bounds read 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 · high confidence

An out-of-bounds read vulnerability exists in Intel XMM 7560 Modem software versions prior to M2_7560_R_01.2146.00. A privileged user with adjacent physical access to the affected device can potentially exploit this to achieve escalation of privilege.

MitigationUpdate Intel XMM 7560 Modem software to version M2_7560_R_01.2146.00 or later. Restrict physical access to devices with this modem component and limit privileged user access as a defense-in-depth measure.

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

CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:N/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. Confirm Intel XMM 7560 Modem is present
    Identify whether the target system or device contains an Intel XMM 7560 modem component. Check system hardware inventory, device specifications, or modem interface output for this specific model number.
    Affected if The system does not contain an Intel XMM 7560 Modem, then this CVE does not apply.
  2. Determine modem firmware version
    Access the modem firmware information through the device management interface, AT command interface, or system diagnostics. Query the modem for its current firmware version string.
    Affected if Unable to retrieve the firmware version from the modem, making version comparison impossible.
  3. Compare installed version to the affected range
    Take the retrieved firmware version and compare it against the vulnerable range: versions prior to M2_7560_R_01.2146.00. Note that version M2_7560_R_01.2146.00 and later are not affected.
    Affected if The installed firmware version is older than M2_7560_R_01.2146.00 (for example, M2_7560_R_01.2145.00 or earlier).
  4. Assess physical access exposure
    Evaluate whether the device with the Intel XMM 7560 modem is deployed in a location where adjacent physical access by untrusted individuals is possible.
    Affected if The device is physically accessible to untrusted or unprivileged personnel in close proximity.
  5. Verify privileged user access controls
    Review user account privileges on the system hosting or managing the modem to determine if non-administrative or untrusted users have elevated privileges.
    Affected if Untrusted or low-privilege users have privileged access to the system managing the modem.

A user is affected if their device contains an Intel XMM 7560 Modem running firmware version earlier than M2_7560_R_01.2146.00, and an untrusted user with physical proximity could gain privileged access to that 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. Restrict physical access to devices with this modem component and limit privileged user access as a defense-in-depth measure.

Recommended fix High confidence

M2_7560_R_01.2146.00 or later

  1. 1. Identify all Intel XMM 7560 Modem devices in the infrastructure requiring remediation
  2. 2. Download the updated firmware version M2_7560_R_01.2146.00 or later from Intel's support website
  3. 3. Follow Intel's standard firmware update procedure for the XMM 7560 Modem
  4. 4. Verify the firmware has been successfully applied by checking the modem's version information
  5. 5. Confirm the vulnerability is resolved through version verification

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-26369 — 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-26369 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