<?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:04:57 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99517</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99517</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvmet: fix use-after-free of the old registrant in nvmet_pr_preempt()&lt;/p&gt;
&lt;p&gt;nvmet_pr_preempt() handles a preempt sent by the reservation holder by
changing the reservation type with nvmet_pr_update_reg_attr(), unless
the reservation is of an All Registrants type.  For the holder that
helper does not modify the registrant in place: it puts a copy on the
registrant list, points pr-&amp;gt;holder to the copy and passes the old
registrant to kfree_rcu().&lt;/p&gt;
&lt;p&gt;If the reservation type changed, nvmet_pr_preempt() then hands
&amp;amp;reg-&amp;gt;hostid of that old registrant to nvmet_pr_resv_released().  Unless
the reservation released notification is masked, that function takes
subsys-&amp;gt;lock and compares the host id against every controller of the
subsystem.  The caller only holds pr-&amp;gt;pr_sem and is not in an RCU
read-side critical section, so nothing keeps the old registrant alive
while it is read.&lt;/p&gt;
&lt;p&gt;The result is a read of 16 freed bytes that decides which controllers
get the notification.  Found by code inspection.  kfree_rcu() defers
the free, so it usually happens after the read; when the pending free
is forced to run before the read, KASAN reports the host id as freed
memory.&lt;/p&gt;
&lt;p&gt;Pass the host id of the controller that sent the command instead.  The
registrant was looked up by that host id, and the controller outlives
the request.&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;nvmet: fix use-after-free of the old registrant in nvmet_pr_preempt()&lt;/p&gt;
&lt;p&gt;nvmet_pr_preempt() handles a preempt sent by the reservation holder by
changing the reservation type with nvmet_pr_update_reg_attr(), unless
the reservation is of an All Registrants type.  For the holder that
helper does not modify the registrant in place: it puts a copy on the
registrant list, points pr-&amp;gt;holder to the copy and passes the old
registrant to kfree_rcu().&lt;/p&gt;
&lt;p&gt;If the reservation type changed, nvmet_pr_preempt() then hands
&amp;amp;reg-&amp;gt;hostid of that old registrant to nvmet_pr_resv_released().  Unless
the reservation released notification is masked, that function takes
subsys-&amp;gt;lock and compares the host id against every controller of the
subsystem.  The caller only holds pr-&amp;gt;pr_sem and is not in an RCU
read-side critical section, so nothing keeps the old registrant alive
while it is read.&lt;/p&gt;
&lt;p&gt;The result is a read of 16 freed bytes that decides which controllers
get the notification.  Found by code inspection.  kfree_rcu() defers
the free, so it usually happens after the read; when the pending free
is forced to run before the read, KASAN reports the host id as freed
memory.&lt;/p&gt;
&lt;p&gt;Pass the host id of the controller that sent the command instead.  The
registrant was looked up by that host id, and the controller outlives
the request.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99517</guid>
    </item>
    <item>
      <title>GHSA-95x2-84p8-24hm</title>
      <link>https://db.gcve.eu/vuln/ghsa-95x2-84p8-24hm</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvmet: fix use-after-free of the old registrant in nvmet_pr_preempt()&lt;/p&gt;
&lt;p&gt;nvmet_pr_preempt() handles a preempt sent by the reservation holder by
changing the reservation type with nvmet_pr_update_reg_attr(), unless
the reservation is of an All Registrants type.  For the holder that
helper does not modify the registrant in place: it puts a copy on the
registrant list, points pr-&amp;gt;holder to the copy and passes the old
registrant to kfree_rcu().&lt;/p&gt;
&lt;p&gt;If the reservation type changed, nvmet_pr_preempt() then hands
&amp;amp;reg-&amp;gt;hostid of that old registrant to nvmet_pr_resv_released().  Unless
the reservation released notification is masked, that function takes
subsys-&amp;gt;lock and compares the host id against every controller of the
subsystem.  The caller only holds pr-&amp;gt;pr_sem and is not in an RCU
read-side critical section, so nothing keeps the old registrant alive
while it is read.&lt;/p&gt;
&lt;p&gt;The result is a read of 16 freed bytes that decides which controllers
get the notification.  Found by code inspection.  kfree_rcu() defers
the free, so it usually happens after the read; when the pending free
is forced to run before the read, KASAN reports the host id as freed
memory.&lt;/p&gt;
&lt;p&gt;Pass the host id of the controller that sent the command instead.  The
registrant was looked up by that host id, and the controller outlives
the request.&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;nvmet: fix use-after-free of the old registrant in nvmet_pr_preempt()&lt;/p&gt;
&lt;p&gt;nvmet_pr_preempt() handles a preempt sent by the reservation holder by
changing the reservation type with nvmet_pr_update_reg_attr(), unless
the reservation is of an All Registrants type.  For the holder that
helper does not modify the registrant in place: it puts a copy on the
registrant list, points pr-&amp;gt;holder to the copy and passes the old
registrant to kfree_rcu().&lt;/p&gt;
&lt;p&gt;If the reservation type changed, nvmet_pr_preempt() then hands
&amp;amp;reg-&amp;gt;hostid of that old registrant to nvmet_pr_resv_released().  Unless
the reservation released notification is masked, that function takes
subsys-&amp;gt;lock and compares the host id against every controller of the
subsystem.  The caller only holds pr-&amp;gt;pr_sem and is not in an RCU
read-side critical section, so nothing keeps the old registrant alive
while it is read.&lt;/p&gt;
&lt;p&gt;The result is a read of 16 freed bytes that decides which controllers
get the notification.  Found by code inspection.  kfree_rcu() defers
the free, so it usually happens after the read; when the pending free
is forced to run before the read, KASAN reports the host id as freed
memory.&lt;/p&gt;
&lt;p&gt;Pass the host id of the controller that sent the command instead.  The
registrant was looked up by that host id, and the controller outlives
the request.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-95x2-84p8-24hm</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>
