LiveActive security incident?Get immediate response
CVE Record

CVE-2021-31532: NXP LPC55S6x microcontrollers (0A and 1B), i.MX RT500 (silicon rev B1 and B2), i.MX RT600 (silicon rev A0,...

NXP LPC55S6x microcontrollers (0A and 1B), i.MX RT500 (silicon rev B1 and B2), i.MX RT600 (silicon rev A0, B0), LPC55S6x, LPC55S2x, LPC552x (silicon rev 0A, 1B), LPC55S1x, LPC551x (silicon rev 0A) and LPC55S0x, LPC550x (silicon rev 0A) include an undocumented ROM patch peripheral that allows unsigned, non-persistent modification of the internal ROM.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE concerns several NXP microcontroller families with an undocumented ROM patch peripheral that can modify internal ROM without signatures. The bundle does not provide CVSS, exploit prerequisites, or a vendor fix. Treat it as an embedded hardware trust issue requiring inventory and vendor confirmation.

Executive priority

Prioritize discovery and vendor engagement over emergency response. Escalate for products where these MCUs anchor secure boot, cryptographic identity, or field-update trust, because undocumented ROM modification challenges core hardware assurance assumptions.

Technical view

Affected NXP LPC55S6x, LPC55S2x, LPC552x, LPC55S1x, LPC551x, LPC55S0x, LPC550x, i.MX RT500, and i.MX RT600 silicon revisions include an undocumented ROM patch peripheral allowing unsigned, non-persistent internal ROM modification. Required access level, persistence boundaries, and remediation details are not stated in the provided sources.

Likely exposure

Exposure is limited to products or lab assets embedding the named NXP microcontrollers and silicon revisions. Organizations without these components are unlikely to be affected. Confirm through hardware BOMs, board designs, firmware teams, and supplier records.

Exploitation context

The provided bundle does not cite active exploitation, and KEV is false. Public evidence identifies the undocumented capability, but does not define real-world attack frequency, prerequisites, or whether remote exploitation is possible.

Researcher notes

Evidence is sparse: the CVE description names affected silicon and capability, but not CVSS, CWE, access vector, exploit chain, or remediation. Avoid assuming persistence or remote reachability. Use vendor and Oxide references as starting points for deeper hardware analysis.

Mitigation direction

  • Inventory products using the listed NXP MCU families and silicon revisions.
  • Check NXP guidance for advisories, errata, lifecycle controls, or silicon updates.
  • Review firmware trust assumptions that depend on immutable internal ROM behavior.
  • Prioritize devices handling secrets, secure boot, device identity, or safety-critical functions.
  • Engage suppliers if the MCU is inside third-party embedded hardware.

Validation and detection

  • Confirm MCU family and silicon revision from BOMs or hardware markings.
  • Ask firmware teams whether ROM patch behavior affects boot or trust boundaries.
  • Review vendor documentation for named silicon revisions and ROM patch controls.
  • Check whether affected devices protect debug, provisioning, and physical access paths.
  • Record evidence gaps where source material does not define exploit prerequisites.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-31532 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.