dbcve.org
Xmm 7560 FirmwareOperating system · Intel

CVE-2022-28611

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 input validation 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 · high confidence

Improper input validation vulnerability in Intel XMM 7560 modem software prior to version M2_7560_R_01.2146.00 allows a privileged user with physical access to the device to escalate privileges. The vulnerability stems from insufficient validation of input data in the modem firmware, potentially allowing an attacker to execute code or gain elevated access within the modem subsystem.

MitigationUpdate Intel XMM 7560 modem software to version M2_7560_R_01.2146.00 or later. Since the vulnerability requires physical access and an already-privileged user, combine the firmware update with physical security controls for devices with sensitive configurations.

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
    Check system hardware or modem interface to confirm the device uses an Intel XMM 7560 modem. This may be visible in device manager, system information, or modem diagnostics.
    Affected if The system does not have an Intel XMM 7560 modem installed, then it is not affected by this specific CVE.
  2. Retrieve the modem firmware version
    Access the modem firmware version through vendor-specific commands or diagnostics tools. Typical methods include AT commands such as AT+CGMR or through the modem management interface provided by the device manufacturer.
    Affected if Unable to retrieve a firmware version indicates the modem may not be accessible for version verification.
  3. Compare firmware version against the vulnerable threshold
    Compare the installed firmware version string to M2_7560_R_01.2146.00. The version must be exactly M2_7560_R_01.2146.00 or later (e.g., M2_7560_R_01.2146.00, M2_7560_R_01.2147.00) to be patched.
    Affected if The installed version is lower than M2_7560_R_01.2146.00 (for example, M2_7560_R_01.2145.00 or any earlier release), then the environment is affected by this vulnerability.
  4. Assess physical access and privilege context
    Determine if the device with the Intel XMM 7560 modem is in an environment where an untrusted individual with physical access could obtain privileged user access. Review user privileges and physical security controls around the device.
    Affected if The device is accessible to untrusted physical users and the firmware version is below M2_7560_R_01.2146.00, the privilege escalation attack vector is present.

A system is affected if it contains an Intel XMM 7560 modem with firmware version lower than M2_7560_R_01.2146.00 and the device is accessible to privileged users with physical access.

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. Since the vulnerability requires physical access and an already-privileged user, combine the firmware update with physical security controls for devices with sensitive configurations.

Recommended fix High confidence

M2_7560_R_01.2146.00

  1. Identify and document the current Intel XMM 7560 Modem firmware version installed on the affected system
  2. Access the Intel support website or contact Intel to obtain the fixed firmware version M2_7560_R_01.2146.00
  3. Review the Intel firmware update documentation for the XMM 7560 Modem to understand the update procedure
  4. Follow the vendor-recommended process to flash/update the modem firmware to version M2_7560_R_01.2146.00 or later
  5. Verify the firmware update was successful by checking the new firmware version
  6. Ensure the system is functioning normally after the update

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

Fix this in Xmm 7560 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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