<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T19:48:50.833786+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2022-50727</id>
    <title>CVE-2022-50727 — scsi: efct: Fix possible memleak in efct_device_init()</title>
    <updated>2026-10-07T19:48:50.849790+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>scsi: efct: Fix possible memleak in efct_device_init()</p>
<p>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:</p>
<p>unreferenced object 0xffff8881020ce000 (size 2048):
  comm "modprobe", pid 465, jiffies 4294928222 (age 55.872s)
  backtrace:
    [&lt;0000000021a1ef1b&gt;] kmalloc_trace+0x27/0x110
    [&lt;000000004c3ed51c&gt;] target_register_template+0x4fd/0x7b0 [target_core_mod]
    [&lt;00000000f3393296&gt;] efct_scsi_tgt_driver_init+0x18/0x50 [efct]
    [&lt;00000000115de533&gt;] 0xffffffffc0d90011
    [&lt;00000000d608f646&gt;] do_one_initcall+0xd0/0x4e0
    [&lt;0000000067828cf1&gt;] do_init_module+0x1cc/0x6a0
    ...</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2022-50727"/>
  </entry>
</feed>
