LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50207: ARM: bcm: Fix refcount leak in bcm_kona_smc_init

In the Linux kernel, the following vulnerability has been resolved: ARM: bcm: Fix refcount leak in bcm_kona_smc_init of_find_matching_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak.

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 cleanup bug affecting an ARM Broadcom Kona initialization path. The issue is a leaked internal reference, not a documented remote takeover. The provided sources do not include CVSS, exploitation evidence, or a detailed business impact statement.

Executive priority

Handle through normal kernel maintenance unless your environment includes ARM/Broadcom Kona systems. There is no provided evidence of active exploitation, but affected embedded or appliance fleets should confirm patch coverage.

Technical view

In bcm_kona_smc_init, of_find_matching_node() increments a device-tree node reference. The fix adds of_node_put() when the node is no longer needed, preventing a refcount leak. Sources do not define attack vector, privileges, user interaction, or impact beyond the leak.

Likely exposure

Exposure appears limited to Linux kernels containing the ARM Broadcom Kona SMC code path, especially affected ARM/Broadcom Kona deployments. General Linux servers are less likely exposed unless they run the affected code and versions listed by the CVE source.

Exploitation context

The provided bundle says KEV is false and gives no cited evidence of active exploitation, public weaponization, or exploit availability. The source material also does not describe a practical attacker path.

Researcher notes

Data quality is limited. The CVE records a resolved Linux kernel refcount leak with multiple stable commit references, but no CVSS, CWE, exploit status, or detailed threat model. Avoid broad exposure claims without platform inventory.

Mitigation direction

  • Check vendor kernel advisories for CVE-2022-50207 applicability.
  • Apply Linux stable updates containing the referenced bcm_kona_smc_init fix.
  • Prioritize affected ARM/Broadcom Kona devices over unrelated Linux fleets.
  • Track downstream distribution backports before marking systems remediated.

Validation and detection

  • Inventory Linux kernel versions and ARM Broadcom Kona platform usage.
  • Confirm whether kernel source includes bcm_kona_smc_init.
  • Verify the relevant stable fix commit or downstream backport is present.
  • Record non-applicability for non-ARM or unaffected kernel builds.
Prepared
Confidence
medium
Sources
10

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-2022-50207 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
0ADP providers
9Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb8eb35fd594aa5b635e329d5c8efab8aaceb8619, b8eb35fd594aa5b635e329d5c8efab8aaceb8619, b8eb35fd594aa5b635e329d5c8efab8aaceb8619, b8eb35fd594aa5b635e329d5c8efab8aaceb8619, b8eb35fd594aa5b635e329d5c8efab8aaceb8619, b8eb35fd594aa5b635e329d5c8efab8aaceb8619, b8eb35fd594aa5b635e329d5c8efab8aaceb8619, b8eb35fd594aa5b635e329d5c8efab8aaceb8619unaffected
LinuxLinux3.10, 0, 4.14.291, 4.19.256, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

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