LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50754: apparmor: fix a memleak in multi_transaction_new()

In the Linux kernel, the following vulnerability has been resolved: apparmor: fix a memleak in multi_transaction_new() In multi_transaction_new(), the variable t is not freed or passed out on the failure of copy_from_user(t->data, buf, size), which could lead to a memleak. Fix this bug by adding a put_multi_transaction(t) in the error path.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50754 is a Linux kernel AppArmor memory leak. Under an error condition while copying user data, allocated memory was not released. The documented impact is resource leakage, which can affect system availability over time. No source in the bundle reports active exploitation, remote attack, privilege escalation, or data theft.

Executive priority

Treat as routine-to-elevated Linux maintenance. It is a kernel availability issue, but sources provide no evidence of active exploitation or severe compromise. Patch through normal kernel update channels, prioritizing shared, multi-user, and higher-criticality Linux hosts.

Technical view

The flaw is in AppArmor multi_transaction_new(). If copy_from_user(t->data, buf, size) fails, object t was neither freed nor returned, causing a kernel memory leak. The upstream fix adds put_multi_transaction(t) on the error path. The source bundle provides multiple stable kernel fix commits, but no CVSS, CWE, or detailed exploitability analysis.

Likely exposure

Linux systems using affected kernel builds with AppArmor code present may be exposed. The affected-version data in the bundle is incomplete and ambiguous, so exposure should be verified against kernel source commits and distribution advisories.

Exploitation context

The public record describes a failure-path memory leak. It does not state active exploitation, public exploit availability, remote reachability, or required privileges. Practical risk is most likely availability impact if an attacker can repeatedly trigger the vulnerable path.

Researcher notes

Key uncertainty is version mapping. The bundle identifies Linux kernel AppArmor and stable fix commits, but lacks CVSS, CWE, and a clean affected/fixed range. Avoid assuming exploitability beyond the documented memory leak without vendor or upstream confirmation.

Mitigation direction

  • Apply kernel updates from your Linux distribution or kernel vendor.
  • Confirm updates include the referenced upstream stable AppArmor fix commits.
  • Prioritize internet-facing or multi-user Linux systems after vendor confirmation.
  • If no vendor advisory exists, monitor vendor guidance for backported fixes.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Check whether AppArmor is enabled or included in deployed kernels.
  • Compare deployed kernel packages with vendor advisories and upstream fix commits.
  • Verify patched systems after reboot are running the updated kernel.
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-50754 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
0Timeline events
0ADP providers
9Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1dea3b41e84c5923173fe654dcb758a5cb4a46e5, 1dea3b41e84c5923173fe654dcb758a5cb4a46e5, 1dea3b41e84c5923173fe654dcb758a5cb4a46e5, 1dea3b41e84c5923173fe654dcb758a5cb4a46e5, 1dea3b41e84c5923173fe654dcb758a5cb4a46e5, 1dea3b41e84c5923173fe654dcb758a5cb4a46e5, 1dea3b41e84c5923173fe654dcb758a5cb4a46e5, 1dea3b41e84c5923173fe654dcb758a5cb4a46e5unaffected
LinuxLinux4.13, 0, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 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.