LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47067: soc/tegra: regulators: Fix locking up when voltage-spread is out of range

In the Linux kernel, the following vulnerability has been resolved: soc/tegra: regulators: Fix locking up when voltage-spread is out of range Fix voltage coupler lockup which happens when voltage-spread is out of range due to a bug in the code. The max-spread requirement shall be accounted when CPU regulator doesn't have consumers. This problem is observed on Tegra30 Ouya game console once system-wide DVFS is enabled in a device-tree.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel availability bug affecting Tegra regulator handling. Under a specific voltage-spread condition, the system can lock up. The public record cites observation on a Tegra30 Ouya console when system-wide DVFS is enabled. Business urgency depends on whether you run affected Tegra-based Linux devices.

Executive priority

Prioritize if you operate Tegra-based embedded, appliance, or edge devices where lockups affect service availability. For typical server or workstation fleets without Tegra hardware, urgency is likely low, but evidence is incomplete.

Technical view

The Tegra regulator voltage coupler could lock up when voltage-spread is out of range. The fix accounts for the max-spread requirement when the CPU regulator has no consumers. The CVE record provides no CVSS, CWE, or exploit evidence, and links stable kernel commits as the resolution.

Likely exposure

Exposure appears limited to Linux systems using NVIDIA Tegra regulator code, especially configurations with system-wide DVFS and affected kernel versions. The source bundle does not identify broad enterprise software exposure or remote attack paths.

Exploitation context

There is no KEV listing and no cited source claims active exploitation. The described impact is a lockup caused by regulator/DVFS behavior, not a documented remote compromise path.

Researcher notes

The record is sparse: no CVSS, CWE, exploit details, or detailed affected range semantics beyond Linux kernel references. Analysis should focus on kernel ancestry, Tegra regulator configuration, and whether the stable commits are present in downstream vendor kernels.

Mitigation direction

  • Inventory Tegra-based Linux devices and their kernel versions.
  • Apply vendor or upstream kernel updates containing the referenced stable fix.
  • Review device-tree DVFS and regulator configuration for affected platforms.
  • Check vendor advisories for platform-specific backports or firmware guidance.

Validation and detection

  • Confirm whether deployed kernels include the referenced stable commits.
  • Test affected Tegra hardware with DVFS enabled in staging.
  • Monitor for regulator, voltage coupler, or unexplained lockup symptoms.
  • Verify any vendor kernel package maps to the fixed upstream change.
Prepared
Confidence
medium
Sources
6

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-47067 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
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux783807436f363e5b1ad4d43ba7debbedfcadbb99, 783807436f363e5b1ad4d43ba7debbedfcadbb99, 783807436f363e5b1ad4d43ba7debbedfcadbb99, 783807436f363e5b1ad4d43ba7debbedfcadbb99unaffected
LinuxLinux5.5, 0, 5.10.37, 5.11.21, 5.12.4, 5.13affected
Weakness

CWE details

No CWE listed

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