<?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>Wed, 30 Sep 2026 19:00:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93067 — drm/bridge: tc358767: clamp the reported AUX read size to the request</title>
      <link>https://db.gcve.eu/vuln/cve-2026-93067</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/bridge: tc358767: clamp the reported AUX read size to the request&lt;/p&gt;
&lt;p&gt;tc_aux_transfer() clamps an AUX read to the payload limit:&lt;/p&gt;
&lt;p&gt;size_t size = min_t(size_t, DP_AUX_MAX_PAYLOAD_BYTES - 1, msg-&amp;gt;size);&lt;/p&gt;
&lt;p&gt;After the transfer it replaces size with the byte count the controller
reports in AUX_BYTES:&lt;/p&gt;
&lt;p&gt;if (size)
		size = FIELD_GET(AUX_BYTES, auxstatus);&lt;/p&gt;
&lt;p&gt;AUX_BYTES is GENMASK(15, 8), so it can be up to 255. Nothing clamps it
back to the request. tc_aux_read_data() reads that many bytes into the
16-byte auxrdata stack buffer, then copies them into the caller buffer. A
reported count of 255 makes the read run to 256 bytes and overruns both.&lt;/p&gt;
&lt;p&gt;The controller should never report more than it was asked to transfer, so
this is defense in depth rather than a live hole. The reported count is
only lightly trusted, and the check is cheap. Clamp it back to the request,
the same way ti-sn65dsi86 does in commit aca58eac52b8 (&amp;#34;drm/bridge:
ti-sn65dsi86: Never store more than msg-&amp;gt;size bytes in AUX xfer&amp;#34;).&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/bridge: tc358767: clamp the reported AUX read size to the request&lt;/p&gt;
&lt;p&gt;tc_aux_transfer() clamps an AUX read to the payload limit:&lt;/p&gt;
&lt;p&gt;size_t size = min_t(size_t, DP_AUX_MAX_PAYLOAD_BYTES - 1, msg-&amp;gt;size);&lt;/p&gt;
&lt;p&gt;After the transfer it replaces size with the byte count the controller
reports in AUX_BYTES:&lt;/p&gt;
&lt;p&gt;if (size)
		size = FIELD_GET(AUX_BYTES, auxstatus);&lt;/p&gt;
&lt;p&gt;AUX_BYTES is GENMASK(15, 8), so it can be up to 255. Nothing clamps it
back to the request. tc_aux_read_data() reads that many bytes into the
16-byte auxrdata stack buffer, then copies them into the caller buffer. A
reported count of 255 makes the read run to 256 bytes and overruns both.&lt;/p&gt;
&lt;p&gt;The controller should never report more than it was asked to transfer, so
this is defense in depth rather than a live hole. The reported count is
only lightly trusted, and the check is cheap. Clamp it back to the request,
the same way ti-sn65dsi86 does in commit aca58eac52b8 (&amp;#34;drm/bridge:
ti-sn65dsi86: Never store more than msg-&amp;gt;size bytes in AUX xfer&amp;#34;).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-93067</guid>
    </item>
  </channel>
</rss>
