linux-cve-announce - CVE-2022-50727: scsi: efct: Fix possible memleak in efct_device

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <2025122419-CVE-2022-50727-95aa@gregkh>
Date: Wed, 24 Dec 2025 13:26:26 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50727: scsi: efct: Fix possible memleak in efct_device_init()

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

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

In the Linux kernel, the following vulnerability has been resolved:

scsi: efct: Fix possible memleak in efct_device_init()

In efct_device_init(), when efct_scsi_reg_fc_transport() fails,
efct_scsi_tgt_driver_exit() is not called to release memory for
efct_scsi_tgt_driver_init() and causes memleak:

unreferenced object 0xffff8881020ce000 (size 2048):
  comm "modprobe", pid 465, jiffies 4294928222 (age 55.872s)
  backtrace:
    [<0000000021a1ef1b>] kmalloc_trace+0x27/0x110
    [<000000004c3ed51c>] target_register_template+0x4fd/0x7b0 [target_core_mod]
    [<00000000f3393296>] efct_scsi_tgt_driver_init+0x18/0x50 [efct]
    [<00000000115de533>] 0xffffffffc0d90011
    [<00000000d608f646>] do_one_initcall+0xd0/0x4e0
    [<0000000067828cf1>] do_init_module+0x1cc/0x6a0
    ...

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


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

	Issue introduced in 5.14 with commit 4df84e8466242de835416a4ec0c856c0e2ed26eb and fixed in 5.15.86 with commit 038359eeccffaf0de4c1c9c51ee19cc5649619a1
	Issue introduced in 5.14 with commit 4df84e8466242de835416a4ec0c856c0e2ed26eb and fixed in 6.0.16 with commit 0c6e6bb30229b1297ac0fd7ede2941d2322fc736
	Issue introduced in 5.14 with commit 4df84e8466242de835416a4ec0c856c0e2ed26eb and fixed in 6.1.2 with commit c7e96168a8ca3be96c4959475164bef31115f07e
	Issue introduced in 5.14 with commit 4df84e8466242de835416a4ec0c856c0e2ed26eb and fixed in 6.2 with commit bb0cd225dd37df1f4a22e36dad59ff33178ecdfc

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-50727
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:
	drivers/scsi/elx/efct/efct_driver.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/038359eeccffaf0de4c1c9c51ee19cc5649619a1
	https://git.kernel.org/stable/c/0c6e6bb30229b1297ac0fd7ede2941d2322fc736
	https://git.kernel.org/stable/c/c7e96168a8ca3be96c4959475164bef31115f07e
	https://git.kernel.org/stable/c/bb0cd225dd37df1f4a22e36dad59ff33178ecdfc