LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49210: MIPS: pgalloc: fix memory leak caused by pgd_free()

In the Linux kernel, the following vulnerability has been resolved: MIPS: pgalloc: fix memory leak caused by pgd_free() pgd page is freed by generic implementation pgd_free() since commit f9cb654cb550 ("asm-generic: pgalloc: provide generic pgd_free()"), however, there are scenarios that the system uses more than one page as the pgd table, in such cases the generic implementation pgd_free() won't be applicable anymore. For example, when PAGE_SIZE_4KB is enabled and MIPS_VA_BITS_48 is not enabled in a 64bit system, the macro "PGD_ORDER" will be set as "1", which will cause allocating two pages as the pgd table. Well, at the same time, the generic implementation pgd_free() just free one pgd page, which will result in the memory leak. The memory leak can be easily detected by executing shell command: "while true; do ls > /dev/null; grep MemFree /proc/meminfo; done"

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory leak affecting some MIPS configurations. A local user can cause repeated page-directory allocation and incomplete freeing, gradually reducing available memory. The main business risk is service instability or denial of service on affected MIPS-based systems, not data theft or privilege escalation.

Executive priority

Treat as a moderate availability issue. Patch during the next kernel maintenance window, faster for MIPS systems that host shared workloads, customer-facing services, or constrained embedded environments where memory leaks can cause outages quickly.

Technical view

The issue is in MIPS page-table allocation cleanup. After generic pgd_free() was introduced, some MIPS configurations still allocate more than one page for a PGD table. The generic free path releases only one page, leaking the rest. CVSS is 5.5 with local, low-complexity, low-privilege availability impact.

Likely exposure

Exposure is most likely on Linux systems using MIPS, especially 64-bit builds with 4KB pages and PGD_ORDER set to allocate multiple PGD pages. The source bundle does not identify affected distributions, cloud images, appliances, or hardware vendors.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not report active exploitation. The described impact requires local ability to trigger process activity that exercises the leaking allocation path. The result is memory exhaustion risk, not confidentiality or integrity compromise.

Researcher notes

Key evidence points to CWE-401 and a MIPS-specific pgd_free() mismatch after commit f9cb654cb550. The provided metadata does not prove remote reachability, public exploitation, or distribution package status. Validate exposure by architecture, kernel lineage, and configuration rather than CVE presence alone.

Mitigation direction

  • Upgrade to a vendor-supported kernel containing the referenced stable fixes.
  • Prioritize internet-facing appliances or embedded systems using MIPS Linux.
  • Restrict untrusted local shell or workload access where patching is delayed.
  • Monitor vendor advisories for distribution-specific fixed package versions.

Validation and detection

  • Inventory systems running Linux on MIPS hardware or MIPS-based appliances.
  • Check kernel version and vendor advisories against CVE-2022-49210.
  • Review kernel configuration for affected MIPS page-size and virtual-address settings.
  • Monitor memory availability trends on suspected affected systems before patching.
Prepared
Confidence
high
Sources
7

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.

cwe · low confidence lookup

CWE-401: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-49210 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
6Source links

SSVC decision data

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2022-49210Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf9cb654cb550b7b87e8608b14fc3eca432429ffe, f9cb654cb550b7b87e8608b14fc3eca432429ffe, f9cb654cb550b7b87e8608b14fc3eca432429ffe, f9cb654cb550b7b87e8608b14fc3eca432429ffe, f9cb654cb550b7b87e8608b14fc3eca432429ffeunaffected
LinuxLinux5.9, 0, 5.10.110, 5.15.33, 5.16.19, 5.17.2, 5.18affected
Weakness

CWE details

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

CWE-401 · source CWE mapping

Missing Release of Memory after Effective Lifetime

Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.