LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50088: mm/damon/reclaim: fix potential memory leak in damon_reclaim_init()

In the Linux kernel, the following vulnerability has been resolved: mm/damon/reclaim: fix potential memory leak in damon_reclaim_init() damon_reclaim_init() allocates a memory chunk for ctx with damon_new_ctx(). When damon_select_ops() fails, ctx is not released, which will lead to a memory leak. We should release the ctx with damon_destroy_ctx() when damon_select_ops() fails to fix the memory leak.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50088 is a Linux kernel defect where a failed DAMON reclaim initialization can leave allocated memory unreleased. The public record describes a memory leak, not code execution, privilege escalation, or data exposure. Business urgency depends on whether affected Linux kernel versions are deployed.

Executive priority

Handle through normal kernel patch management unless vendor guidance raises severity. There is no source evidence of exploitation or a high-impact security primitive, but affected systems should still receive maintained kernel updates.

Technical view

The issue is in mm/damon/reclaim. damon_reclaim_init() allocates a DAMON context with damon_new_ctx(); if damon_select_ops() fails, that context was not destroyed. The fix releases it with damon_destroy_ctx() on the failure path.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions listed in the CVE data, including 5.18-related releases, 5.19.2, and 6.0. The source bundle does not identify specific distributions, configurations, or packaged kernel advisories.

Exploitation context

No active exploitation is reported in the provided sources, and the CVE is not marked KEV. The available evidence only supports a potential kernel memory leak during a DAMON reclaim initialization failure path.

Researcher notes

The record is sparse: no CVSS, CWE, exploit details, or distro matrix are provided. Analysis should stay tied to the upstream fix path and vendor package status. Avoid assuming reachability beyond the documented DAMON reclaim initialization failure path.

Mitigation direction

  • Check vendor kernel advisories for affected packaged versions.
  • Update to a kernel containing the referenced stable fixes.
  • Prioritize internet-facing or memory-constrained Linux hosts after vendor confirmation.
  • Track distribution backports rather than relying only on upstream version numbers.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Check whether deployed kernels include the referenced stable commits.
  • Review vendor advisories for distribution-specific affected packages.
  • Monitor systems for unusual kernel memory pressure if patching is delayed.
Prepared
Confidence
medium
Sources
5

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-50088 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
4Source 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
LinuxLinux4d69c3457821100a39fa8c6e0c23ed910bb6c29d, 4d69c3457821100a39fa8c6e0c23ed910bb6c29d, 4d69c3457821100a39fa8c6e0c23ed910bb6c29dunaffected
LinuxLinux5.18, 0, 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.