LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50249: memory: of: Fix refcount leak bug in of_get_ddr_timings()

In the Linux kernel, the following vulnerability has been resolved: memory: of: Fix refcount leak bug in of_get_ddr_timings() We should add the of_node_put() when breaking out of for_each_child_of_node() as it will automatically increase and decrease the refcount.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50249 is a Linux kernel refcount leak in DDR timing handling. The public record does not provide CVSS, CWE, or confirmed security impact. Treat it as a kernel maintenance vulnerability requiring patch tracking, not as evidence of an active breach or urgent internet-facing exploit.

Executive priority

Handle through routine kernel patch management unless the environment depends heavily on affected kernel builds or shows stability symptoms. There is no supplied evidence of exploitation or a quantified severity score.

Technical view

The issue is in of_get_ddr_timings(). When breaking out of for_each_child_of_node(), the code needed of_node_put() to release the child node reference. Stable kernel commits address the leak across multiple maintained branches. The source does not describe privilege requirements, attacker control, or demonstrated impact.

Likely exposure

Exposure depends on running Linux kernel versions listed as affected in the CVE data, including several stable branch points through 6.1. Systems not using the relevant kernel code path may have limited practical exposure, but the source bundle does not define affected configurations in detail.

Exploitation context

No active exploitation is stated. The CVE bundle marks KEV as false and provides no exploit reports, proof of exploitation, or attack preconditions. Any claim beyond a refcount leak would exceed the supplied evidence.

Researcher notes

The useful research gap is impact analysis: the record identifies the leak and fix, but not exploitability, reachable hardware profiles, or security consequences. Validate against upstream commits and downstream distribution backports.

Mitigation direction

  • Track the relevant Linux stable commit for your kernel branch.
  • Apply vendor or distribution kernel updates that include the fix.
  • Check Linux distributor advisories before assuming downstream impact.
  • Prioritize normally unless internal testing shows stability impact.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Map each kernel to vendor advisories or listed stable commits.
  • Confirm patched builds include the of_get_ddr_timings() refcount fix.
  • Monitor kernel logs for unexplained memory or stability issues.
Prepared
Confidence
medium
Sources
11

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-50249 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
10Source 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
LinuxLinuxe6b42eb6a66c188642aeb447312938c6f6ebee86, e6b42eb6a66c188642aeb447312938c6f6ebee86, e6b42eb6a66c188642aeb447312938c6f6ebee86, e6b42eb6a66c188642aeb447312938c6f6ebee86, e6b42eb6a66c188642aeb447312938c6f6ebee86, e6b42eb6a66c188642aeb447312938c6f6ebee86, e6b42eb6a66c188642aeb447312938c6f6ebee86, e6b42eb6a66c188642aeb447312938c6f6ebee86, e6b42eb6a66c188642aeb447312938c6f6ebee86unaffected
LinuxLinux3.7, 0, 4.9.331, 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

No CWE listed

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