<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 20 Nov 2026 21:03:45 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99765</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99765</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: target: Fix demo-mode dynamic ACL dev-entry UAF vs LUN teardown&lt;/p&gt;
&lt;p&gt;A demo-mode (generate_node_acls=1) login that allocates a dynamic NodeACL
populates that ACL&amp;#39;s per-LUN dev entries in core_tpg_add_node_to_devs()
*before* the ACL is linked onto tpg-&amp;gt;acl_node_list by
target_add_node_acl():&lt;/p&gt;
&lt;p&gt;core_tpg_check_initiator_node_acl():
		...
		core_tpg_add_node_to_devs(acl, tpg, NULL); /* builds deves */
		target_add_node_acl(acl);                  /* only now listed */&lt;/p&gt;
&lt;p&gt;The LUN teardown sweep, core_clear_lun_from_tpg(), enumerates only
tpg-&amp;gt;acl_node_list, so a dev entry whose ACL is still in the window above
is invisible to the sweep and is never disabled.  It is left on the
se_lun-&amp;gt;lun_deve_list after core_tpg_remove_lun() frees the se_lun; when
the same unpacked_lun is later re-added and the se_lun is reallocated at
the same address, the stale dev entry is rediscovered by
target_nacl_find_deve() and core_enable_device_list_for_node() corrupts
lun_deve_list:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free ...
   core_enable_device_list_for_node+0x5ce/0x880
   core_tpg_add_node_to_devs+0x169/0x190
   core_dev_add_lun+0x146/0x190
   target_fabric_port_link+0xe9/0x1b0
   configfs_symlink+0x381/0xae0
   __x64_sys_symlink+0x55/0x80&lt;/p&gt;
&lt;p&gt;The demo-mode login path that drives the ACL/dev-entry creation is
reachable by an unauthenticated initiator; the colliding LUN add/remove is
a local configfs operation.&lt;/p&gt;
&lt;p&gt;Commit 49cb77e297dc (&amp;#34;targe…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: target: Fix demo-mode dynamic ACL dev-entry UAF vs LUN teardown&lt;/p&gt;
&lt;p&gt;A demo-mode (generate_node_acls=1) login that allocates a dynamic NodeACL
populates that ACL&amp;#39;s per-LUN dev entries in core_tpg_add_node_to_devs()
*before* the ACL is linked onto tpg-&amp;gt;acl_node_list by
target_add_node_acl():&lt;/p&gt;
&lt;p&gt;core_tpg_check_initiator_node_acl():
		...
		core_tpg_add_node_to_devs(acl, tpg, NULL); /* builds deves */
		target_add_node_acl(acl);                  /* only now listed */&lt;/p&gt;
&lt;p&gt;The LUN teardown sweep, core_clear_lun_from_tpg(), enumerates only
tpg-&amp;gt;acl_node_list, so a dev entry whose ACL is still in the window above
is invisible to the sweep and is never disabled.  It is left on the
se_lun-&amp;gt;lun_deve_list after core_tpg_remove_lun() frees the se_lun; when
the same unpacked_lun is later re-added and the se_lun is reallocated at
the same address, the stale dev entry is rediscovered by
target_nacl_find_deve() and core_enable_device_list_for_node() corrupts
lun_deve_list:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free ...
   core_enable_device_list_for_node+0x5ce/0x880
   core_tpg_add_node_to_devs+0x169/0x190
   core_dev_add_lun+0x146/0x190
   target_fabric_port_link+0xe9/0x1b0
   configfs_symlink+0x381/0xae0
   __x64_sys_symlink+0x55/0x80&lt;/p&gt;
&lt;p&gt;The demo-mode login path that drives the ACL/dev-entry creation is
reachable by an unauthenticated initiator; the colliding LUN add/remove is
a local configfs operation.&lt;/p&gt;
&lt;p&gt;Commit 49cb77e297dc (&amp;#34;targe…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99765</guid>
    </item>
    <item>
      <title>GHSA-7p8r-jg48-9546</title>
      <link>https://db.gcve.eu/vuln/ghsa-7p8r-jg48-9546</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: target: Fix demo-mode dynamic ACL dev-entry UAF vs LUN teardown&lt;/p&gt;
&lt;p&gt;A demo-mode (generate_node_acls=1) login that allocates a dynamic NodeACL
populates that ACL&amp;#39;s per-LUN dev entries in core_tpg_add_node_to_devs()
*before* the ACL is linked onto tpg-&amp;gt;acl_node_list by
target_add_node_acl():&lt;/p&gt;
&lt;p&gt;core_tpg_check_initiator_node_acl():
		...
		core_tpg_add_node_to_devs(acl, tpg, NULL); /* builds deves */
		target_add_node_acl(acl);                  /* only now listed */&lt;/p&gt;
&lt;p&gt;The LUN teardown sweep, core_clear_lun_from_tpg(), enumerates only
tpg-&amp;gt;acl_node_list, so a dev entry whose ACL is still in the window above
is invisible to the sweep and is never disabled.  It is left on the
se_lun-&amp;gt;lun_deve_list after core_tpg_remove_lun() frees the se_lun; when
the same unpacked_lun is later re-added and the se_lun is reallocated at
the same address, the stale dev entry is rediscovered by
target_nacl_find_deve() and core_enable_device_list_for_node() corrupts
lun_deve_list:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free ...
   core_enable_device_list_for_node+0x5ce/0x880
   core_tpg_add_node_to_devs+0x169/0x190
   core_dev_add_lun+0x146/0x190
   target_fabric_port_link+0xe9/0x1b0
   configfs_symlink+0x381/0xae0
   __x64_sys_symlink+0x55/0x80&lt;/p&gt;
&lt;p&gt;The demo-mode login path that drives the ACL/dev-entry creation is
reachable by an unauthenticated initiator; the colliding LUN add/remove is
a local configfs operation.&lt;/p&gt;
&lt;p&gt;Commit 49cb77e297dc (&amp;#34;targe…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: target: Fix demo-mode dynamic ACL dev-entry UAF vs LUN teardown&lt;/p&gt;
&lt;p&gt;A demo-mode (generate_node_acls=1) login that allocates a dynamic NodeACL
populates that ACL&amp;#39;s per-LUN dev entries in core_tpg_add_node_to_devs()
*before* the ACL is linked onto tpg-&amp;gt;acl_node_list by
target_add_node_acl():&lt;/p&gt;
&lt;p&gt;core_tpg_check_initiator_node_acl():
		...
		core_tpg_add_node_to_devs(acl, tpg, NULL); /* builds deves */
		target_add_node_acl(acl);                  /* only now listed */&lt;/p&gt;
&lt;p&gt;The LUN teardown sweep, core_clear_lun_from_tpg(), enumerates only
tpg-&amp;gt;acl_node_list, so a dev entry whose ACL is still in the window above
is invisible to the sweep and is never disabled.  It is left on the
se_lun-&amp;gt;lun_deve_list after core_tpg_remove_lun() frees the se_lun; when
the same unpacked_lun is later re-added and the se_lun is reallocated at
the same address, the stale dev entry is rediscovered by
target_nacl_find_deve() and core_enable_device_list_for_node() corrupts
lun_deve_list:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free ...
   core_enable_device_list_for_node+0x5ce/0x880
   core_tpg_add_node_to_devs+0x169/0x190
   core_dev_add_lun+0x146/0x190
   target_fabric_port_link+0xe9/0x1b0
   configfs_symlink+0x381/0xae0
   __x64_sys_symlink+0x55/0x80&lt;/p&gt;
&lt;p&gt;The demo-mode login path that drives the ACL/dev-entry creation is
reachable by an unauthenticated initiator; the colliding LUN add/remove is
a local configfs operation.&lt;/p&gt;
&lt;p&gt;Commit 49cb77e297dc (&amp;#34;targe…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-7p8r-jg48-9546</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
