dbcve.org
Scp FirmwareOperating system · Arm

CVE-2024-11863

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 2.16.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Specifically crafted SCMI messages sent to an SCP running SCP-Firmware release versions up to and including 2.15.0 may lead to a Usage Fault and crash the SCP

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

This is a firmware vulnerability in SCP-Firmware (System Control Processor Firmware) where specifically crafted SCMI (System Control and Management Interface) messages can trigger a Usage Fault and crash the SCP. The SCP is a critical ARM processor responsible for system control and management functions. Versions up to and including 2.15.0 are affected.

MitigationUpdate SCP-Firmware to a version beyond 2.15.0 (if available) following the vendor's firmware update procedure, ensuring the update is tested in a staging environment first due to the critical nature of the SCP component.

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
Scp FirmwareOperating system
Affected:< 2.16.0

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 if SCP-Firmware is present on the system
    Check system documentation, firmware manifests, or boot logs for references to 'SCP', 'System Control Processor', or 'scp-firmware'. On ARM-based servers, this is often found in MORELLO, Neoverse, or other reference platforms.
    Affected if The system utilizes an SCP for system control and management functions.
  2. Determine the installed SCP-Firmware version
    Query the SCP firmware version through available interfaces: (1) Check /sys/class/misc or device tree entries for scmiver or version info, (2) Use vendor-specific IPMI commands or BMC interfaces (e.g., 'ipmi fru print' or similar), (3) Review firmware dump metadata if accessible via debug ports. Compare the discovered version against the affected range (< 2.16.0).
    Affected if The installed SCP-Firmware version is 2.15.0 or earlier.
  3. Verify SCMI message handling configuration
    Inspect the SCP-Firmware build configuration or device tree for SCMI protocol handlers. Check whether the SCMI message handler validates message sources or accepts messages only from trusted agents (e.g., secure world or verified main CPU). Look for configuration flags related to SCMI_SCMI_MESSAGE_VALIDATION or similar.
    Affected if SCMI messages from untrusted or external sources are accepted without proper validation.
  4. Assess attack surface for SCMI message injection
    Review system architecture to determine what can send SCMI messages to the SCP. Check if debug interfaces (JTAG, UART), network-accessible BMC/IPMI interfaces, or untrusted guest VMs have direct or indirect paths to send SCMI messages to the SCP.
    Affected if Untrusted or external entities have the ability to send arbitrary SCMI messages to the SCP.

A system is affected if it runs SCP-Firmware version 2.15.0 or earlier AND has any pathway that allows untrusted actors to inject specially crafted SCMI messages to the System Control Processor.

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
Upgrade available Upgrade to 2.16.0 or later
Fixed in 2.16.0
Interim mitigation

Update SCP-Firmware to a version beyond 2.15.0 (if available) following the vendor's firmware update procedure, ensuring the update is tested in a staging environment first due to the critical nature of the SCP component.

Recommended fix High confidence

SCP-Firmware 2.16.0 or later

  1. Identify the current SCP-Firmware version in use by checking the firmware build or system documentation
  2. Obtain SCP-Firmware version 2.16.0 or later from the official Arm developer resources (developer.arm.com)
  3. Follow the platform-specific firmware update procedure to apply the new SCP-Firmware image
  4. Verify the upgrade was successful by confirming the running SCP-Firmware version is 2.16.0 or later
Caveat Firmware upgrades carry inherent risk; ensure backup and rollback procedures are in place before applying

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

Fix this in Scp Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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