LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50284: ipc: fix memory leak in init_mqueue_fs()

In the Linux kernel, the following vulnerability has been resolved: ipc: fix memory leak in init_mqueue_fs() When setup_mq_sysctls() failed in init_mqueue_fs(), mqueue_inode_cachep is not released. In order to fix this issue, the release path is reordered.

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

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel memory leak in POSIX message queue filesystem initialization. If a setup step fails, kernel memory allocated for the message queue inode cache may not be released. The source does not provide CVSS, active exploitation evidence, or a business-impact chain.

Executive priority

Set this to normal patch-cycle priority unless your Linux vendor assigns higher severity. There is no source-backed evidence of active exploitation, but kernel memory leaks still matter for platform reliability and should not be ignored.

Technical view

init_mqueue_fs() can leak mqueue_inode_cachep when setup_mq_sysctls() fails. The resolved kernel change reorders the release path so allocated cache state is cleaned up on failure. Public sources identify Linux kernel versions and stable commits, but do not describe exploitability beyond the leak.

Likely exposure

Exposure appears limited to systems running affected Linux kernel builds listed by the CVE source. The source lists 5.19, 6.0.16, 6.1.2, 6.2, and an ambiguous 0 entry; validate against your distribution’s kernel advisories.

Exploitation context

The provided sources do not show active exploitation, public weaponization, or inclusion in CISA KEV. Treat this as a kernel reliability and resource-management issue unless vendor guidance adds stronger impact evidence.

Researcher notes

The public record is sparse: no CVSS, CWE, exploit status, or detailed attacker preconditions are provided. Analysis should focus on kernel version mapping, distro backports, and whether local vendor kernels include the stable cleanup-path fix.

Mitigation direction

  • Check Linux distribution advisories for CVE-2022-50284 coverage.
  • Update affected kernels through the supported vendor channel.
  • Confirm the deployed kernel includes one of the referenced stable fixes.
  • Prioritize internet-facing or multi-tenant Linux hosts if vendor severity increases.

Validation and detection

  • Inventory running kernel versions across Linux assets.
  • Compare versions against vendor advisories and the CVE affected data.
  • Verify patched kernels include the referenced stable commit lineage.
  • Monitor CVE and vendor pages for severity or exploit-status updates.
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-50284 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
LinuxLinuxdc55e35f9e810f23dd69cfdc91a3d636023f57a2, dc55e35f9e810f23dd69cfdc91a3d636023f57a2, dc55e35f9e810f23dd69cfdc91a3d636023f57a2unaffected
LinuxLinux5.19, 0, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

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