<?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-03T12:07:38.673890+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-98815</id>
    <title>fkie_cve-2026-98815</title>
    <updated>2026-11-03T12:07:38.708934+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>nvme: fix cdev lifetime</p>
<p>Sashiko bot reported a potential problem for the cdev lifetime in [0]
- the code there is heavily based on the NVMe code.</p>
<p>Currently the NS head .open and .release file_operations methods take and
put a reference to the nvme_ns_head to ensure that this structure does not
disappear while we open fds for that cdev.</p>
<p>In multipath mode, when we teardown the NS head, we call nvme_cdev_del() -&gt;
cdev_device_del() -&gt; cdev_del(). However after cdev_del() returns, cdevs
already open will remain and their fops will still be callable. As such,
we can still reference the cdev after the nvme_ns_head reference count
drops to 0 (and is freed).</p>
<p>This can be shown with an application which delays between opening the cdev
and issuing the ioctl while the NS head is being torn down:</p>
<p># ./ioctl_file /dev/ng1n1 &amp;
# waiting 10 seconds ....</p>
<p># ./ini_nvme_teardown.sh
[   21.221718] nvme nvme1: Removing ctrl: NQN "nvme-test-target"
[   21.274609] nvme nvme2: Removing ctrl: NQN "nvme-test-target"
# now going to issue ioctl ....
[   26.549285] ==================================================================
[   26.550841] BUG: KASAN: slab-use-after-free in cdev_put.part.0+0x3d/0x40
[   26.552352] Read of size 8 at addr ffff88811e7fa170 by task ioctl_file/237
[   26.553805]
[   26.554227] CPU: 3 UID: 0 PID: 237 Comm: ioctl_file Not tainted 7.2.0-rc1-00004-g6852a10e32d4 #921 PREEMPT(lazy)
[   26.554236] Hardwar…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-98815"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-x2m3-gxmv-qw6j</id>
    <title>GHSA-x2m3-gxmv-qw6j</title>
    <updated>2026-11-03T12:07:38.709040+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>nvme: fix cdev lifetime</p>
<p>Sashiko bot reported a potential problem for the cdev lifetime in [0]
- the code there is heavily based on the NVMe code.</p>
<p>Currently the NS head .open and .release file_operations methods take and
put a reference to the nvme_ns_head to ensure that this structure does not
disappear while we open fds for that cdev.</p>
<p>In multipath mode, when we teardown the NS head, we call nvme_cdev_del() -&gt;
cdev_device_del() -&gt; cdev_del(). However after cdev_del() returns, cdevs
already open will remain and their fops will still be callable. As such,
we can still reference the cdev after the nvme_ns_head reference count
drops to 0 (and is freed).</p>
<p>This can be shown with an application which delays between opening the cdev
and issuing the ioctl while the NS head is being torn down:</p>
<p># ./ioctl_file /dev/ng1n1 &amp;
# waiting 10 seconds ....</p>
<p># ./ini_nvme_teardown.sh
[   21.221718] nvme nvme1: Removing ctrl: NQN "nvme-test-target"
[   21.274609] nvme nvme2: Removing ctrl: NQN "nvme-test-target"
# now going to issue ioctl ....
[   26.549285] ==================================================================
[   26.550841] BUG: KASAN: slab-use-after-free in cdev_put.part.0+0x3d/0x40
[   26.552352] Read of size 8 at addr ffff88811e7fa170 by task ioctl_file/237
[   26.553805]
[   26.554227] CPU: 3 UID: 0 PID: 237 Comm: ioctl_file Not tainted 7.2.0-rc1-00004-g6852a10e32d4 #921 PREEMPT(lazy)
[   26.554236] Hardwar…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-x2m3-gxmv-qw6j"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/msrc_cve-2026-98815</id>
    <title>msrc_CVE-2026-98815 — nvme: fix cdev lifetime</title>
    <updated>2026-11-03T12:07:38.709092+00:00</updated>
    <content>msrc_CVE-2026-98815</content>
    <link href="https://db.gcve.eu/vuln/msrc_cve-2026-98815"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ubuntu-cve-2026-98815</id>
    <title>UBUNTU-CVE-2026-98815</title>
    <updated>2026-11-03T12:07:38.709117+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 248 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: nvme: fix cdev lifetime Sashiko bot reported a potential problem for the cdev lifetime in [0] - the code there is heavily based on the NVMe code. Currently the NS head .open and .release file_operations methods take and put a reference to the nvme_ns_head to ensure that this structure does not disappear while we open fds for that cdev. In multipath mode, when we teardown the NS head, we call nvme_cdev_del() -&gt; cdev_device_del() -&gt; cdev_del(). However after cdev_del() returns, cdevs already open will remain and their fops will still be callable. As such, we can still reference the cdev after the nvme_ns_head reference count drops to 0 (and is freed). This can be shown with an application which delays between opening the cdev and issuing the ioctl while the NS head is being torn down: # ./ioctl_file /dev/ng1n1 &amp; # waiting 10 seconds .... # ./ini_nvme_teardown.sh [   21.221718] nvme nvme1: Removing ctrl: NQN "nvme-test-target" [   21.274609] nvme nvme2: Removing ctrl: NQN "nvme-test-target" # now going to issue ioctl .... [   26.549285] ================================================================== [   26.550841] BUG: KASAN: slab-use-after-free in cdev_put.part.0+0x3d/0x40 [   26.552352] Read of size 8 at addr ffff88811e7fa170 by task ioctl_file/237 [   26.553805] [   26.554227] CPU: 3 UID: 0 PID: 237 Comm: ioctl_file Not tainted 7.2.0-rc1-00004-g6852a10e32d4 #921 PREEMPT(lazy) [   26.554236] Hardware name:…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ubuntu-cve-2026-98815"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/wid-sec-w-2026-4019</id>
    <title>WID-SEC-W-2026-4019 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-11-03T12:07:38.709441+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-4019"/>
  </entry>
</feed>
