LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50751: configfs: fix possible memory leak in configfs_create_dir()

In the Linux kernel, the following vulnerability has been resolved: configfs: fix possible memory leak in configfs_create_dir() kmemleak reported memory leaks in configfs_create_dir(): unreferenced object 0xffff888009f6af00 (size 192): comm "modprobe", pid 3777, jiffies 4295537735 (age 233.784s) backtrace: kmem_cache_alloc (mm/slub.c:3250 mm/slub.c:3256 mm/slub.c:3263 mm/slub.c:3273) new_fragment (./include/linux/slab.h:600 fs/configfs/dir.c:163) configfs_register_subsystem (fs/configfs/dir.c:1857) basic_write (drivers/hwtracing/stm/p_basic.c:14) stm_p_basic do_one_initcall (init/main.c:1296) do_init_module (kernel/module/main.c:2455) ... unreferenced object 0xffff888003ba7180 (size 96): comm "modprobe", pid 3777, jiffies 4295537735 (age 233.784s) backtrace: kmem_cache_alloc (mm/slub.c:3250 mm/slub.c:3256 mm/slub.c:3263 mm/slub.c:3273) configfs_new_dirent (./include/linux/slab.h:723 fs/configfs/dir.c:194) configfs_make_dirent (fs/configfs/dir.c:248) configfs_create_dir (fs/configfs/dir.c:296) configfs_attach_group.isra.28 (fs/configfs/dir.c:816 fs/configfs/dir.c:852) configfs_register_subsystem (fs/configfs/dir.c:1881) basic_write (drivers/hwtracing/stm/p_basic.c:14) stm_p_basic do_one_initcall (init/main.c:1296) do_init_module (kernel/module/main.c:2455) ... This is because the refcount is not correct in configfs_make_dirent(). For normal stage, the refcount is changing as: configfs_register_subsystem() configfs_create_dir() configfs_make_dirent() configfs_new_dirent() # set s_count = 1 dentry->d_fsdata = configfs_get(sd); # s_count = 2 ... configfs_unregister_subsystem() configfs_remove_dir() remove_dir() configfs_remove_dirent() # s_count = 1 dput() ... *dentry_unlink_inode()* configfs_d_iput() # s_count = 0, release However, if we failed in configfs_create(): configfs_register_subsystem() configfs_create_dir() configfs_make_dirent() # s_count = 2 ... configfs_create() # fail ->out_remove: configfs_remove_dirent(dentry) configfs_put(sd) # s_count = 1 return PTR_ERR(inode); There is no inode in the error path, so the configfs_d_iput() is lost and makes sd and fragment memory leaked. To fix this, when we failed in configfs_create(), manually call configfs_put(sd) to keep the refcount correct.

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-50751 is a Linux kernel memory leak in configfs error handling. When directory creation fails, references are not released correctly. The main business concern is stability or resource exhaustion on affected systems, not confirmed data theft or remote compromise. No active exploitation is indicated in the provided sources.

Executive priority

Handle through normal kernel patch management unless your environment exposes configfs-related functionality to untrusted users. There is no source-backed evidence of active exploitation or remote compromise, but affected long-lived servers should receive vendor-confirmed kernel updates.

Technical view

The flaw is in configfs_create_dir()/configfs_make_dirent() reference counting. If configfs_create() fails, the error path removes one reference but misses the dentry inode cleanup path, leaving configfs_dirent and fragment memory unreleased. Kernel stable commits add an explicit configfs_put(sd) on failure.

Likely exposure

Exposure is limited to Linux kernels containing the vulnerable configfs code. The source bundle lists affected Linux versions including 2.6.16, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, and 6.2. Validate against your distribution kernel, not only upstream version numbers.

Exploitation context

The provided evidence describes a memory leak observed by kmemleak during module initialization paths involving configfs subsystem registration. It does not show remote reachability, privilege requirements, public exploit availability, or active exploitation. CISA KEV status is false in the bundle.

Researcher notes

The CVE record is unusually dated in the future in the supplied bundle. Severity, CVSS, and CWE are absent. The vulnerability is a refcount imbalance on the configfs_create() failure path, fixed across multiple stable branches by adding the missing put operation.

Mitigation direction

  • Identify Linux systems using affected kernel builds.
  • Apply vendor or distribution kernel updates containing the referenced stable fixes.
  • If no advisory exists, ask the OS vendor to confirm backport status.
  • Prioritize systems where untrusted users can trigger relevant kernel module or configfs paths.

Validation and detection

  • Check running kernel versions and distribution patch levels.
  • Compare kernel source or changelog for the referenced configfs fix commits.
  • Review vendor advisories for CVE-2022-50751 backport confirmation.
  • Monitor kernel logs and memory-leak diagnostics where available.
Prepared
Confidence
medium
Sources
8

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-50751 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
7Source 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
LinuxLinux7063fbf2261194f72ee75afca67b3b38b554b5fa, 7063fbf2261194f72ee75afca67b3b38b554b5fa, 7063fbf2261194f72ee75afca67b3b38b554b5fa, 7063fbf2261194f72ee75afca67b3b38b554b5fa, 7063fbf2261194f72ee75afca67b3b38b554b5fa, 7063fbf2261194f72ee75afca67b3b38b554b5faunaffected
LinuxLinux2.6.16, 0, 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.