linux-cve-announce - CVE-2022-50376: orangefs: Fix kmemleak in orangefs_{kernel,client}_debug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025091850-CVE-2022-50376-1398@gregkh>
Date: Thu, 18 Sep 2025 15:33:50 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50376: orangefs: Fix kmemleak in orangefs_{kernel,client}_debug_init()

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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.

The Linux kernel CVE team has assigned CVE-2022-50376 to this issue.


Affected and fixed versions
===========================

	Fixed in 5.4.229 with commit bdc2d33fa2324b1f5ab5b701cda45ee0b2384409
	Fixed in 5.10.163 with commit a076490b0211990ec6764328c22cb744dd782bd9
	Fixed in 5.15.86 with commit c8853267289c55b1acbe4dc3641374887584834d
	Fixed in 6.0.16 with commit 786e5296f9e3b045d5ff9098514ce7b8ba1d890d
	Fixed in 6.1.2 with commit 0cd303aad220fafa595e0ed593e99aa51b90412b
	Fixed in 6.2 with commit 31720a2b109b3080eb77e97b8f6f50a27b4ae599

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2022-50376
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	fs/orangefs/orangefs-debugfs.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/bdc2d33fa2324b1f5ab5b701cda45ee0b2384409
	https://git.kernel.org/stable/c/a076490b0211990ec6764328c22cb744dd782bd9
	https://git.kernel.org/stable/c/c8853267289c55b1acbe4dc3641374887584834d
	https://git.kernel.org/stable/c/786e5296f9e3b045d5ff9098514ce7b8ba1d890d
	https://git.kernel.org/stable/c/0cd303aad220fafa595e0ed593e99aa51b90412b
	https://git.kernel.org/stable/c/31720a2b109b3080eb77e97b8f6f50a27b4ae599