LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50391: mm/mempolicy: fix memory leak in set_mempolicy_home_node system call

In the Linux kernel, the following vulnerability has been resolved: mm/mempolicy: fix memory leak in set_mempolicy_home_node system call When encountering any vma in the range with policy other than MPOL_BIND or MPOL_PREFERRED_MANY, an error is returned without issuing a mpol_put on the policy just allocated with mpol_dup(). This allows arbitrary users to leak kernel memory.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a local Linux kernel memory leak. A user who can run code on an affected system may repeatedly trigger leaked kernel memory, potentially exhausting resources and disrupting availability. It is not described as a remote compromise or data theft issue.

Executive priority

Treat as a moderate operational risk. It is unlikely to be an internet-facing breach vector from the provided evidence, but it can affect availability on systems with local users. Patch through normal kernel maintenance, prioritizing shared or exposed execution environments.

Technical view

CVE-2022-50391 affects Linux kernel mm/mempolicy handling in set_mempolicy_home_node. An error path after mpol_dup() can return without mpol_put() when a VMA policy is not MPOL_BIND or MPOL_PREFERRED_MANY, causing a kernel memory leak. CVSS is 5.5 with local, low-complexity, low-privilege access and high availability impact.

Likely exposure

Exposure is most relevant on affected Linux kernels where non-root local users can execute code. Shared servers, developer systems, and multi-user workloads deserve attention. The supplied version data is incomplete, so confirm exact exposure against kernel or distribution advisories.

Exploitation context

The source bundle does not indicate active exploitation, and KEV is false. The weakness is local and availability-focused: an arbitrary user may leak kernel memory. No cited source supports remote exploitation, privilege escalation, confidentiality impact, or integrity impact.

Researcher notes

Focus review on mm/mempolicy error handling around set_mempolicy_home_node and policy reference lifecycle. The provided commits identify the upstream stable fixes, but the source bundle does not provide detailed distro backport mapping or exploit telemetry.

Mitigation direction

  • Apply Linux stable or distribution kernel updates containing the referenced fixes.
  • Check vendor guidance for exact package versions and backports.
  • Limit untrusted local shell or code execution until patched.
  • Monitor affected hosts for unusual memory pressure or availability degradation.

Validation and detection

  • Inventory running kernel versions across Linux hosts.
  • Compare kernels against vendor advisories and the referenced stable commits.
  • Prioritize systems allowing local access by untrusted users.
  • Confirm patched kernels are booted, not only installed.
Prepared
Confidence
medium
Sources
5

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-50391 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
0Timeline events
0ADP providers
4Source links

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.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2022-50391Attack 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc6018b4b254971863bd0ad36bb5e7d0fa0f0ddb0, c6018b4b254971863bd0ad36bb5e7d0fa0f0ddb0, c6018b4b254971863bd0ad36bb5e7d0fa0f0ddb0unaffected
LinuxLinux5.17, 0, 6.0.17, 6.1.3, 6.2affected
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.