<?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-10-27T21:16:35.186539+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/cve-2026-98964</id>
    <title>CVE-2026-98964 — nvmet: use the local P2P device on metadata allocation failure</title>
    <updated>2026-10-27T21:16:35.195185+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>nvmet: use the local P2P device on metadata allocation failure</p>
<p>nvmet_req_alloc_p2pmem_sgls() assigns req-&gt;p2p_dev only after the data
and metadata SGL allocations succeed. If the data allocation succeeds
but the metadata allocation fails, out_free_sg passes req-&gt;p2p_dev to
pci_p2pmem_free_sgl() before that assignment has taken place.</p>
<p>Pass the local p2p_dev argument instead, so cleanup uses the same PCI
device as the successful data allocation.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-98964"/>
  </entry>
</feed>
