https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 01 Nov 2026 19:31:56 +0000 https://db.gcve.eu/vuln/certfr-2026-avi-1375 certfr-2026-avi-1375 https://db.gcve.eu/vuln/certfr-2026-avi-1375 https://db.gcve.eu/vuln/fkie_cve-2026-98727 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known</p> <p>The namespace head is marked zoned at allocation time based only on the command set identifier. If the zone info query reports a zero zone size, the path namespace is registered without zoned limits while the head still advertises the zoned capability with a zone size of zero, and reporting zones or writing to the head then shifts by ilog2(0).</p> <p>Drop the zoned feature from the head allocation and let the head limits refresh stack it in from the path namespace instead.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known</p> <p>The namespace head is marked zoned at allocation time based only on the command set identifier. If the zone info query reports a zero zone size, the path namespace is registered without zoned limits while the head still advertises the zoned capability with a zone size of zero, and reporting zones or writing to the head then shifts by ilog2(0).</p> <p>Drop the zoned feature from the head allocation and let the head limits refresh stack it in from the path namespace instead.</p> https://db.gcve.eu/vuln/fkie_cve-2026-98727 https://db.gcve.eu/vuln/ghsa-7665-pcff-x7hw <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known</p> <p>The namespace head is marked zoned at allocation time based only on the command set identifier. If the zone info query reports a zero zone size, the path namespace is registered without zoned limits while the head still advertises the zoned capability with a zone size of zero, and reporting zones or writing to the head then shifts by ilog2(0).</p> <p>Drop the zoned feature from the head allocation and let the head limits refresh stack it in from the path namespace instead.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known</p> <p>The namespace head is marked zoned at allocation time based only on the command set identifier. If the zone info query reports a zero zone size, the path namespace is registered without zoned limits while the head still advertises the zoned capability with a zone size of zero, and reporting zones or writing to the head then shifts by ilog2(0).</p> <p>Drop the zoned feature from the head allocation and let the head limits refresh stack it in from the path namespace instead.</p> https://db.gcve.eu/vuln/ghsa-7665-pcff-x7hw https://db.gcve.eu/vuln/msrc_cve-2026-98727 msrc_CVE-2026-98727 https://db.gcve.eu/vuln/msrc_cve-2026-98727 https://db.gcve.eu/vuln/ubuntu-cve-2026-98727 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known The namespace head is marked zoned at allocation time based only on the command set identifier. If the zone info query reports a zero zone size, the path namespace is registered without zoned limits while the head still advertises the zoned capability with a zone size of zero, and reporting zones or writing to the head then shifts by ilog2(0). Drop the zoned feature from the head allocation and let the head limits refresh stack it in from the path namespace instead.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known The namespace head is marked zoned at allocation time based only on the command set identifier. If the zone info query reports a zero zone size, the path namespace is registered without zoned limits while the head still advertises the zoned capability with a zone size of zero, and reporting zones or writing to the head then shifts by ilog2(0). Drop the zoned feature from the head allocation and let the head limits refresh stack it in from the path namespace instead.</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-98727