LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50779: orangefs: Fix kmemleak in orangefs_prepare_debugfs_help_string()

In the Linux kernel, the following vulnerability has been resolved: orangefs: Fix kmemleak in orangefs_prepare_debugfs_help_string() When insert and remove the orangefs module, then debug_help_string will be leaked: unreferenced object 0xffff8881652ba000 (size 4096): comm "insmod", pid 1701, jiffies 4294893639 (age 13218.530s) hex dump (first 32 bytes): 43 6c 69 65 6e 74 20 44 65 62 75 67 20 4b 65 79 Client Debug Key 77 6f 72 64 73 20 61 72 65 20 75 6e 6b 6e 6f 77 words are unknow backtrace: [<0000000004e6f8e3>] kmalloc_trace+0x27/0xa0 [<0000000006f75d85>] orangefs_prepare_debugfs_help_string+0x5e/0x480 [orangefs] [<0000000091270a2a>] _sub_I_65535_1+0x57/0xf70 [crc_itu_t] [<000000004b1ee1a3>] do_one_initcall+0x87/0x2a0 [<000000001d0614ae>] do_init_module+0xdf/0x320 [<00000000efef068c>] load_module+0x2f98/0x3330 [<000000006533b44d>] __do_sys_finit_module+0x113/0x1b0 [<00000000a0da6f99>] do_syscall_64+0x35/0x80 [<000000007790b19b>] entry_SYSCALL_64_after_hwframe+0x46/0xb0 When remove the module, should always free debug_help_string. Should always free the allocated buffer when change the free_debug_help_string.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50779 is a Linux kernel OrangeFS memory leak. Repeatedly inserting and removing the OrangeFS module can leak a small allocated buffer. The public record does not show active exploitation or a remote attack path. Business urgency is generally low unless systems rely on OrangeFS or allow frequent privileged module operations.

Executive priority

Treat as a low-priority kernel hygiene item. Patch during normal maintenance, with higher priority for systems using OrangeFS or environments where privileged users routinely load and unload kernel modules.

Technical view

The issue is in orangefs_prepare_debugfs_help_string(). A debug_help_string buffer allocated during module initialization was not always freed when the OrangeFS module was removed or the free_debug_help_string state changed. The upstream stable fixes add cleanup for the allocated buffer. The CVE record lists Linux kernel versions as affected, but severity and CVSS are not provided.

Likely exposure

Exposure is most relevant to Linux systems using or capable of loading the OrangeFS kernel module on affected kernel builds. Practical triggering appears to require module insertion and removal, which normally requires elevated local privileges. Systems without OrangeFS present or loadable are likely less exposed.

Exploitation context

No CISA KEV entry is indicated, and the supplied sources do not report active exploitation. The described condition is a kernel memory leak during module lifecycle handling, not a documented privilege escalation or remote code execution path.

Researcher notes

Evidence indicates a kmemleak finding, with a 4096-byte unreferenced object after OrangeFS module insertion and removal. The source bundle does not provide CVSS, CWE, exploitability analysis, or distribution-specific package status, so exposure assessment depends on local kernel builds and vendor backports.

Mitigation direction

  • Update to a vendor kernel containing the referenced upstream stable OrangeFS fix.
  • If OrangeFS is unused, prevent the module from being loaded where operationally safe.
  • Check Linux distribution advisories for backported fixes and supported package versions.
  • Prioritize routine kernel maintenance over emergency response unless OrangeFS is business-critical.

Validation and detection

  • Inventory Linux kernel versions across affected environments.
  • Check whether the OrangeFS kernel module is present, loaded, or loadable.
  • Compare installed kernels against vendor advisories for this CVE.
  • Confirm patched kernels include one of the referenced stable commits or a vendor backport.
Prepared
Confidence
medium
Sources
11

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-50779 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
10Source 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
LinuxLinuxdc0336214eb07ee9de2a41dd4c81c744ffa419ac, dc0336214eb07ee9de2a41dd4c81c744ffa419ac, dc0336214eb07ee9de2a41dd4c81c744ffa419ac, dc0336214eb07ee9de2a41dd4c81c744ffa419ac, dc0336214eb07ee9de2a41dd4c81c744ffa419ac, dc0336214eb07ee9de2a41dd4c81c744ffa419ac, dc0336214eb07ee9de2a41dd4c81c744ffa419ac, dc0336214eb07ee9de2a41dd4c81c744ffa419ac, dc0336214eb07ee9de2a41dd4c81c744ffa419acunaffected
LinuxLinux4.9, 0, 4.9.337, 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.