CVE-2022-50727
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 ...
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Memory leak in Linux kernel efct driver when efct_scsi_reg_fc_transport() fails, leading to unreleased memory.
Description
In the Linux kernel's efct (FC SCSI target) driver, the function efct_device_init() fails to properly release memory when efct_scsi_reg_fc_transport() returns an error. Specifically, if this registration fails, the cleanup function efct_scsi_tgt_driver_exit() is not called, leaving the memory allocated by efct_scsi_tgt_driver_init() unreferenced. This memory leak has been observed during module loading and can be seen in kernel memory debug output, showing a 2048-byte allocation that is not freed [1].
Exploitability
The vulnerability can be triggered when the efct driver module is loaded and the call to register the FC transport fails. An attacker would need to be able to influence the module loading or the state of the FC transport registration to cause the failure. However, given that this is a bug in error handling, it may be exploitable by an unprivileged user if they can trigger an error condition during driver initialization, e.g., by manipulating system resources or configuration.
Impact
A successful trigger results in a memory leak. Over repeated module load/unload cycles or under specific error conditions, this could lead to memory exhaustion, potentially causing system instability or denial of service. The leak is relatively small per occurrence (2048 bytes) but can accumulate.
Mitigation
The fix has been applied in the Linux kernel stable branch via commit bb0cd225dd37df1f4a22e36dad59ff33178ecdfc [1]. Users should update to a kernel version containing this patch. No workaround is mentioned; however, avoiding error conditions during driver initialization may reduce risk.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
4038359eeccff0c6e6bb30229c7e96168a8cabb0cd225dd37Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
4News mentions
0No linked articles in our index yet.