CVE-2022-50727
Last modified
CVE-2022-50727 is a vulnerability of currently unknown severity. 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 .... EPSS estimates a 0.21% chance of exploitation in the next 30 days.
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 ...
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 4df84e8466242de835416a4ec0c856c0e2ed26eb, < 038359eeccffaf0de4c1c9c51ee19cc5649619a1; >= 4df84e8466242de835416a4ec0c856c0e2ed26eb, < 0c6e6bb30229b1297ac0fd7ede2941d2322fc736; >= 4df84e8466242de835416a4ec0c856c0e2ed26eb, < c7e96168a8ca3be96c4959475164bef31115f07e; >= 4df84e8466242de835416a4ec0c856c0e2ed26eb, < bb0cd225dd37df1f4a22e36dad59ff33178ecdfc |
| Linux | Linux | 5.14 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2022-50727?
How severe is CVE-2022-50727?
How do I fix CVE-2022-50727?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-50721In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50722In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50723In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50724In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50725In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50726In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50728In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50729In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50730In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50731In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50732In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2022-50733In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2022-50727?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
