LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50147: mm/mempolicy: fix get_nodes out of bound access

In the Linux kernel, the following vulnerability has been resolved: mm/mempolicy: fix get_nodes out of bound access When user specified more nodes than supported, get_nodes will access nmask array out of bounds.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw is an out-of-bounds array access in memory policy handling. A user-supplied node count can exceed what the kernel supports, causing invalid access. The public bundle does not provide impact details, CVSS scoring, or confirmed exploitation, so urgency depends on kernel exposure and vendor advisories.

Executive priority

Treat as a kernel maintenance item with uncertain severity. It should enter normal vulnerability remediation workflows, with higher priority for shared Linux infrastructure, but the public evidence does not justify emergency handling by itself.

Technical view

The issue is in Linux kernel mm/mempolicy get_nodes. When a user specifies more NUMA nodes than supported, get_nodes can access the nmask array out of bounds. The bundle says the vulnerability has been resolved and links stable kernel commits, but does not describe crash, privilege, or confidentiality impact.

Likely exposure

Systems running affected Linux kernel versions or vendor kernels carrying the vulnerable mm/mempolicy code may be exposed. Exposure should be checked against distribution kernel advisories, because the bundle does not map every downstream package or backport.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. It also does not provide exploit prerequisites beyond a user-specified node count reaching vulnerable kernel code.

Researcher notes

Key unknowns are impact, trigger requirements, and affected downstream builds. The source describes an out-of-bounds nmask access in get_nodes and supplies stable commits, but lacks CVSS, CWE, exploitation evidence, and detailed affected-version semantics.

Mitigation direction

  • Check Linux distribution advisories for CVE-2022-50147 and matching kernel packages.
  • Update to a vendor-supported kernel containing the referenced stable fixes.
  • Prioritize multi-user Linux systems until impact is clarified by the vendor.
  • Track whether downstream kernels have backported the mm/mempolicy fix.

Validation and detection

  • Inventory Linux kernel versions across affected servers, containers hosts, and appliances.
  • Compare installed kernels with vendor advisories for CVE-2022-50147.
  • Confirm whether referenced stable commits are present in custom kernel trees.
  • Document unresolved systems where vendor guidance is unavailable or ambiguous.
Prepared
Confidence
medium
Sources
6

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-50147 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
5Source 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
LinuxLinuxe130242dc351f1cfa2bbeb6766a1486ce936ef88, e130242dc351f1cfa2bbeb6766a1486ce936ef88, e130242dc351f1cfa2bbeb6766a1486ce936ef88, e130242dc351f1cfa2bbeb6766a1486ce936ef88unaffected
LinuxLinux5.15, 0, 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.