<?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>Mon, 09 Nov 2026 18:43:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99155 — scsi: xen/scsifront: Check for a NULL shadow entry on a backend response</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99155</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: xen/scsifront: Check for a NULL shadow entry on a backend response&lt;/p&gt;
&lt;p&gt;scsifront_do_response() validates the rqid in a backend response against
VSCSIIF_MAX_REQS before using it to index info-&amp;gt;shadow[], but then
dereferences the entry to test -&amp;gt;inflight without checking that the slot
is populated.  Shadow slots are NULL before a command is submitted (the
host private area is zeroed at allocation) and are reset to NULL in
_scsifront_put_rqid() once a request completes, so an in-range rqid that
does not correspond to an outstanding request makes the frontend
dereference a NULL pointer.&lt;/p&gt;
&lt;p&gt;A malicious or buggy backend can thus crash the guest by returning a
response whose rqid is in range but not in flight -- for example a
spurious response before any command has been issued, or a duplicate of
one already completed.  The ring has only VSCSIIF_MAX_REQS (16) slots,
so before the first command every in-range rqid selects a NULL slot.&lt;/p&gt;
&lt;p&gt;Reject a response whose shadow slot is not populated.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: xen/scsifront: Check for a NULL shadow entry on a backend response&lt;/p&gt;
&lt;p&gt;scsifront_do_response() validates the rqid in a backend response against
VSCSIIF_MAX_REQS before using it to index info-&amp;gt;shadow[], but then
dereferences the entry to test -&amp;gt;inflight without checking that the slot
is populated.  Shadow slots are NULL before a command is submitted (the
host private area is zeroed at allocation) and are reset to NULL in
_scsifront_put_rqid() once a request completes, so an in-range rqid that
does not correspond to an outstanding request makes the frontend
dereference a NULL pointer.&lt;/p&gt;
&lt;p&gt;A malicious or buggy backend can thus crash the guest by returning a
response whose rqid is in range but not in flight -- for example a
spurious response before any command has been issued, or a duplicate of
one already completed.  The ring has only VSCSIIF_MAX_REQS (16) slots,
so before the first command every in-range rqid selects a NULL slot.&lt;/p&gt;
&lt;p&gt;Reject a response whose shadow slot is not populated.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99155</guid>
    </item>
  </channel>
</rss>
