CVE-2022-50727
published 2025-12-24CVE-2022-50727: In the Linux kernel, the following vulnerability has been resolved: scsi: efct: Fix possible memleak in efct_device_init() In efct_device_init(), when…
PriorityP420
EPSS
0.21%
11.8th percentile
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:
[] kmalloc_trace+0x27/0x110
[] target_register_template+0x4fd/0x7b0 [target_core_mod]
[] efct_scsi_tgt_driver_init+0x18/0x50 [efct]
[] 0xffffffffc0d90011
[] do_one_initcall+0xd0/0x4e0
[] do_init_module+0x1cc/0x6a0
...
Affected
12 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.4-1 (bookworm) | linux 6.1.4-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 4df84e8466242de835416a4ec0c856c0e2ed26eb < 038359eeccffaf0de4c1c9c51ee19cc5649619a1 | 038359eeccffaf0de4c1c9c51ee19cc5649619a1 |
| linux | linux | >= 4df84e8466242de835416a4ec0c856c0e2ed26eb < 0c6e6bb30229b1297ac0fd7ede2941d2322fc736 | 0c6e6bb30229b1297ac0fd7ede2941d2322fc736 |
| linux | linux | >= 4df84e8466242de835416a4ec0c856c0e2ed26eb < c7e96168a8ca3be96c4959475164bef31115f07e | c7e96168a8ca3be96c4959475164bef31115f07e |
| linux | linux | >= 4df84e8466242de835416a4ec0c856c0e2ed26eb < bb0cd225dd37df1f4a22e36dad59ff33178ecdfc | bb0cd225dd37df1f4a22e36dad59ff33178ecdfc |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 5.14.0 < 5.15.86 | 5.15.86 |
| linux | linux_kernel | >= 5.16.0 < 6.0.16 | 6.0.16 |
| linux | linux_kernel | >= 6.1.0 < 6.1.2 | 6.1.2 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: scsi: efct: Fix possible memleak in efct_device_init()
vendor_redhat·2025-12-24
CVE-2022-50727 kernel: scsi: efct: Fix possible memleak in efct_device_init()
kernel: scsi: efct: Fix possible memleak in efct_device_init()
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:
[] kmalloc_trace+0x27/0x110
[] target_register_template+0x4fd/0x7b0 [target_core_mod]
[] efct_scsi_tgt_driver_init+0x18/0x50 [efct]
[] 0xffffffffc0d90011
[] do_one_initcall+0xd0/0x4e0
[] do_init_module+0x1cc/0x6a0
...
Package: kernel (Red Hat Enterprise Linux 10) - Not affected
Package: kernel (Red Hat Enterpris
Debian
CVE-2022-50727: linux - In the Linux kernel, the following vulnerability has been resolved: scsi: efct:...
vendor_debian·2022
CVE-2022-50727 CVE-2022-50727: linux - In the Linux kernel, the following vulnerability has been resolved: scsi: efct:...
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: [] kmalloc_trace+0x27/0x110 [] target_register_template+0x4fd/0x7b0 [target_core_mod] [] efct_scsi_tgt_driver_init+0x18/0x50 [efct] [] 0xffffffffc0d90011 [] do_one_initcall+0xd0/0x4e0 [] do_init_module+0x1cc/0x6a0 ...
Scope: local
bookworm: resolved (fixed in 6.1.4-1)
bullseye: resolved
forky: resolved (fixed in 6.1.4-1)
sid: resolved (fixed in 6.1.4-1)
trixie: resolved (fixed
VulDB
Linux Kernel up to 5.15.85/6.0.15/6.1.1 efct_device_init memory leak (Nessus ID 280024 / WID-SEC-2025-2929)
vuldb·2026-04-21
CVE-2022-50727 [CRITICAL] Linux Kernel up to 5.15.85/6.0.15/6.1.1 efct_device_init memory leak (Nessus ID 280024 / WID-SEC-2025-2929)
A vulnerability identified as critical has been detected in Linux Kernel up to 5.15.85/6.0.15/6.1.1. This affects the function efct_device_init. Performing a manipulation results in memory leak.
This vulnerability was named CVE-2022-50727. The attack needs to be approached within the local network. There is no available exploit.
You should upgrade the affected component.
OSV
scsi: efct: Fix possible memleak in efct_device_init()
osv·2025-12-24
CVE-2022-50727 scsi: efct: Fix possible memleak in efct_device_init()
scsi: efct: Fix possible memleak in efct_device_init()
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:
[] kmalloc_trace+0x27/0x110
[] target_register_template+0x4fd/0x7b0 [target_core_mod]
[] efct_scsi_tgt_driver_init+0x18/0x50 [efct]
[] 0xffffffffc0d90011
[] do_one_initcall+0xd0/0x4e0
[] do_init_module+0x1cc/0x6a0
...
OSV
CVE-2022-50727: In the Linux kernel, the following vulnerability has been resolved: scsi: efct: Fix possible memleak in efct_device_init() In efct_device_init(), when
osv·2025-12-24
CVE-2022-50727 CVE-2022-50727: In the Linux kernel, the following vulnerability has been resolved: scsi: efct: Fix possible memleak in efct_device_init() In efct_device_init(), when
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: [] kmalloc_trace+0x27/0x110 [] target_register_template+0x4fd/0x7b0 [target_core_mod] [] efct_scsi_tgt_driver_init+0x18/0x50 [efct] [] 0xffffffffc0d90011 [] do_one_initcall+0xd0/0x4e0 [] do_init_module+0x1cc/0x6a0 ...
GHSA
GHSA-976x-8ghm-5pq3: In the Linux kernel, the following vulnerability has been resolved:
scsi: efct: Fix possible memleak in efct_device_init()
In efct_device_init(), wh
ghsa_unreviewed·2025-12-24
CVE-2022-50727 GHSA-976x-8ghm-5pq3: In the Linux kernel, the following vulnerability has been resolved:
scsi: efct: Fix possible memleak in efct_device_init()
In efct_device_init(), wh
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:
[] kmalloc_trace+0x27/0x110
[] target_register_template+0x4fd/0x7b0 [target_core_mod]
[] efct_scsi_tgt_driver_init+0x18/0x50 [efct]
[] 0xffffffffc0d90011
[] do_one_initcall+0xd0/0x4e0
[] do_init_module+0x1cc/0x6a0
...
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2022-50727 kernel: scsi: efct: Fix possible memleak in efct_device_init()
bugzilla·2025-12-24
CVE-2022-50727 CVE-2022-50727 kernel: scsi: efct: Fix possible memleak in efct_device_init()
CVE-2022-50727 kernel: scsi: efct: Fix possible memleak in efct_device_init()
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:
[] kmalloc_trace+0x27/0x110
[] target_register_template+0x4fd/0x7b0 [target_core_mod]
[] efct_scsi_tgt_driver_init+0x18/0x50 [efct]
[] 0xffffffffc0d90011
[] do_one_initcall+0xd0/0x4e0
[] do_init_module+0x1cc/0x6a0
...
Discussion:
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/202
Wiz
CVE-2022-50727 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz
CVE-2022-50727 CVE-2022-50727 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2022-50727 :
Linux Kernel vulnerability analysis and mitigation
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:
[] kmalloc_trace+0x27/0x110
[] target_register_template+0x4fd/0x7b0 [target_core_mod]
[] efct_scsi_tgt_driver_init+0x18/0x50 [efct]
[] 0xffffffffc0d90011
[] do_one_initcall+0xd0/0x4e0
[] do_init_module+0x1cc/0x6a0
...
Source : NVD
Published December 24, 2025
CNA Score N/A
Affected Technologies
Lin
2025-12-24
Published