<?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>Tue, 29 Sep 2026 14:36:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53552 — drm/i915: mark requests for GuC virtual engines to avoid use-after-free</title>
      <link>https://db.gcve.eu/vuln/cve-2023-53552</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;drm/i915: mark requests for GuC virtual engines to avoid use-after-free&lt;/p&gt;
&lt;p&gt;References to i915_requests may be trapped by userspace inside a
sync_file or dmabuf (dma-resv) and held indefinitely across different
proceses. To counter-act the memory leaks, we try to not to keep
references from the request past their completion.
On the other side on fence release we need to know if rq-&amp;gt;engine
is valid and points to hw engine (true for non-virtual requests).
To make it possible extra bit has been added to rq-&amp;gt;execution_mask,
for marking virtual engines.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 280410677af763f3871b93e794a199cfcf6fb580)&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;drm/i915: mark requests for GuC virtual engines to avoid use-after-free&lt;/p&gt;
&lt;p&gt;References to i915_requests may be trapped by userspace inside a
sync_file or dmabuf (dma-resv) and held indefinitely across different
proceses. To counter-act the memory leaks, we try to not to keep
references from the request past their completion.
On the other side on fence release we need to know if rq-&amp;gt;engine
is valid and points to hw engine (true for non-virtual requests).
To make it possible extra bit has been added to rq-&amp;gt;execution_mask,
for marking virtual engines.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 280410677af763f3871b93e794a199cfcf6fb580)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2023-53552</guid>
    </item>
  </channel>
</rss>
