LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50376: orangefs: Fix kmemleak in orangefs_{kernel,client}_debug_init()

In the Linux kernel, the following vulnerability has been resolved: orangefs: Fix kmemleak in orangefs_{kernel,client}_debug_init() When insert and remove the orangefs module, there are memory leaked as below: unreferenced object 0xffff88816b0cc000 (size 2048): comm "insmod", pid 783, jiffies 4294813439 (age 65.512s) hex dump (first 32 bytes): 6e 6f 6e 65 0a 00 00 00 00 00 00 00 00 00 00 00 none............ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<0000000031ab7788>] kmalloc_trace+0x27/0xa0 [<000000005b405fee>] orangefs_debugfs_init.cold+0xaf/0x17f [<00000000e5a0085b>] 0xffffffffa02780f9 [<000000004232d9f7>] do_one_initcall+0x87/0x2a0 [<0000000054f22384>] do_init_module+0xdf/0x320 [<000000003263bdea>] load_module+0x2f98/0x3330 [<0000000052cd4153>] __do_sys_finit_module+0x113/0x1b0 [<00000000250ae02b>] do_syscall_64+0x35/0x80 [<00000000f11c03c7>] entry_SYSCALL_64_after_hwframe+0x46/0xb0 Use the golbal variable as the buffer rather than dynamic allocate to slove the problem.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50376 is a Linux kernel OrangeFS memory leak triggered around OrangeFS module initialization and removal. The cited impact is availability only, not data theft or tampering. Business urgency is highest for systems that load or permit OrangeFS kernel support, especially shared or multi-user Linux environments.

Executive priority

Treat this as a moderate availability issue. It is not supported as remotely exploitable or actively exploited in the supplied evidence, but it matters for Linux fleets where local users can stress kernel resources or where uptime is critical.

Technical view

The flaw is CWE-401 in orangefs_kernel_debug_init() and orangefs_client_debug_init(). Dynamic allocation during debugfs initialization could leave leaked memory when the OrangeFS module is inserted and removed. The kernel fix replaces dynamic buffers with global buffers. CVSS 3.1 is 5.5: local, low complexity, privileges required, high availability impact.

Likely exposure

Exposure appears limited to Linux systems with affected kernel versions and OrangeFS module code present or loadable. The record does not identify specific distributions, cloud images, or appliances, so asset owners should map vendor kernels to the referenced upstream stable commits.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source claims active exploitation. The CVSS vector indicates local access with privileges required and no user interaction. The practical risk is resource exhaustion or denial of service, not confidentiality or integrity compromise.

Researcher notes

The source evidence is narrow: a kernel memory leak report and stable commit references. The affected-version data is present but not distribution-specific. Validate through kernel source, distro backport metadata, and whether OrangeFS is reachable in the target operating environment.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable OrangeFS fixes.
  • Use distribution or vendor advisories to identify fixed package versions.
  • If OrangeFS is unused, follow vendor-supported guidance to disable or avoid loading it.
  • Limit local accounts and module-management privileges on shared Linux systems.
  • Prioritize remediation where untrusted users have local access.

Validation and detection

  • Inventory Linux kernels and compare them with vendor guidance for CVE-2022-50376.
  • Check whether OrangeFS support is installed, enabled, or loadable on relevant hosts.
  • Confirm deployed kernels include one of the referenced stable commits or vendor backports.
  • Review local user access on systems where affected kernels remain deployed.
Prepared
Confidence
high
Sources
8

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-50376 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
7Source 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-50376Attack 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
LinuxLinuxf7ab093f74bf638ed98fd1115f3efa17e308bb7f, f7ab093f74bf638ed98fd1115f3efa17e308bb7f, f7ab093f74bf638ed98fd1115f3efa17e308bb7f, f7ab093f74bf638ed98fd1115f3efa17e308bb7f, f7ab093f74bf638ed98fd1115f3efa17e308bb7f, f7ab093f74bf638ed98fd1115f3efa17e308bb7funaffected
LinuxLinux4.6, 0, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 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.