<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-20T21:27:36.897992+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/fkie_cve-2026-99517</id>
    <title>fkie_cve-2026-99517</title>
    <updated>2026-11-20T21:27:36.901341+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>nvmet: fix use-after-free of the old registrant in nvmet_pr_preempt()</p>
<p>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-&gt;holder to the copy and passes the old
registrant to kfree_rcu().</p>
<p>If the reservation type changed, nvmet_pr_preempt() then hands
&amp;reg-&gt;hostid of that old registrant to nvmet_pr_resv_released().  Unless
the reservation released notification is masked, that function takes
subsys-&gt;lock and compares the host id against every controller of the
subsystem.  The caller only holds pr-&gt;pr_sem and is not in an RCU
read-side critical section, so nothing keeps the old registrant alive
while it is read.</p>
<p>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.</p>
<p>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.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99517"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-95x2-84p8-24hm</id>
    <title>GHSA-95x2-84p8-24hm</title>
    <updated>2026-11-20T21:27:36.901471+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>nvmet: fix use-after-free of the old registrant in nvmet_pr_preempt()</p>
<p>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-&gt;holder to the copy and passes the old
registrant to kfree_rcu().</p>
<p>If the reservation type changed, nvmet_pr_preempt() then hands
&amp;reg-&gt;hostid of that old registrant to nvmet_pr_resv_released().  Unless
the reservation released notification is masked, that function takes
subsys-&gt;lock and compares the host id against every controller of the
subsystem.  The caller only holds pr-&gt;pr_sem and is not in an RCU
read-side critical section, so nothing keeps the old registrant alive
while it is read.</p>
<p>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.</p>
<p>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.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-95x2-84p8-24hm"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</id>
    <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
    <updated>2026-11-20T21:27:36.901502+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/wid-sec-w-2026-4695"/>
  </entry>
</feed>
