LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50201: selinux: fix memleak in security_read_state_kernel()

In the Linux kernel, the following vulnerability has been resolved: selinux: fix memleak in security_read_state_kernel() In this function, it directly returns the result of __security_read_policy without freeing the allocated memory in *data, cause memory leak issue, so free the memory if __security_read_policy failed. [PM: subject line tweak]

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel SELinux memory leak fix. If an internal policy-read operation fails, allocated memory may not be released. The public record does not provide CVSS, exploit details, or a confirmed business-impact scenario, so urgency should be driven by kernel exposure and standard patch cadence.

Executive priority

Handle through normal kernel vulnerability management unless affected systems are highly sensitive or memory exhaustion would create operational risk. There is not enough public evidence here to justify emergency response by itself.

Technical view

security_read_state_kernel() returned the result of __security_read_policy() directly. On failure, memory allocated in *data was not freed, creating a leak. The fix frees that memory when __security_read_policy() fails. The source identifies Linux kernel versions and stable commits, but not a reachable attack vector.

Likely exposure

Exposure is likely limited to systems running affected Linux kernel versions with SELinux code present. The bundle lists affected Linux versions including 5.12, 5.15.61, 5.18.18, 5.19.2, and 6.0, but distribution-specific package status must be verified.

Exploitation context

No active exploitation is stated in the provided sources, and the CVE is not marked KEV. The bundle does not describe remote exploitation, privilege requirements, or a public proof of concept. Treat exploitability as unconfirmed from these sources.

Researcher notes

The record describes a failure-path memory leak only. The affected-version data is sparse and includes upstream commit references, so map exposure through kernel source history or distro backports. Avoid assuming exploitability beyond the documented leak without additional evidence.

Mitigation direction

  • Identify Linux kernels matching the affected version data in the CVE record.
  • Apply vendor kernel updates that include the referenced stable SELinux fix.
  • For distributions, follow distro security advisories rather than upstream commit assumptions.
  • Prioritize internet-facing or high-availability systems if kernel patch windows are constrained.

Validation and detection

  • Confirm each asset's running kernel version against vendor advisory data.
  • Verify the relevant stable fix is included in the deployed kernel package.
  • Check whether SELinux is enabled or materially used on affected systems.
  • Review monitoring for unusual kernel memory pressure, while noting this is not proof of exploitation.
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-50201 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
LinuxLinuxfdd1ffe8a812b1109388e4bc389e57b2695ad095, fdd1ffe8a812b1109388e4bc389e57b2695ad095, fdd1ffe8a812b1109388e4bc389e57b2695ad095, fdd1ffe8a812b1109388e4bc389e57b2695ad095unaffected
LinuxLinux5.12, 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.