<?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://vulnerability.circl.lu</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 01:11:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68279 — drm/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68279</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/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers&lt;/p&gt;
&lt;p&gt;drm_dp_sideband_parse_remote_dpcd_read() reads num_bytes from the raw
message and then unconditionally does:&lt;/p&gt;
&lt;p&gt;memcpy(bytes, &amp;amp;raw-&amp;gt;msg[idx], num_bytes);&lt;/p&gt;
&lt;p&gt;without checking that idx + num_bytes &amp;lt;= raw-&amp;gt;curlen. raw-&amp;gt;msg[] is
256 bytes; if a malicious or misbehaving MST hub sets num_bytes larger
than the remaining payload, the memcpy reads past the received data
into whatever follows in raw-&amp;gt;msg[].&lt;/p&gt;
&lt;p&gt;drm_dp_sideband_parse_remote_i2c_read_ack() has the same flaw (noted
with a /* TODO check */ comment since the code was introduced).&lt;/p&gt;
&lt;p&gt;Fix both functions by using a single combined check
(idx + num_bytes &amp;gt; curlen) before each memcpy. Since num_bytes is u8,
it is always &amp;gt;= 0, so this strictly subsumes the simpler idx &amp;gt; curlen
form and no separate step is needed.&lt;/p&gt;
&lt;p&gt;[added missing fixes tag]&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/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers&lt;/p&gt;
&lt;p&gt;drm_dp_sideband_parse_remote_dpcd_read() reads num_bytes from the raw
message and then unconditionally does:&lt;/p&gt;
&lt;p&gt;memcpy(bytes, &amp;amp;raw-&amp;gt;msg[idx], num_bytes);&lt;/p&gt;
&lt;p&gt;without checking that idx + num_bytes &amp;lt;= raw-&amp;gt;curlen. raw-&amp;gt;msg[] is
256 bytes; if a malicious or misbehaving MST hub sets num_bytes larger
than the remaining payload, the memcpy reads past the received data
into whatever follows in raw-&amp;gt;msg[].&lt;/p&gt;
&lt;p&gt;drm_dp_sideband_parse_remote_i2c_read_ack() has the same flaw (noted
with a /* TODO check */ comment since the code was introduced).&lt;/p&gt;
&lt;p&gt;Fix both functions by using a single combined check
(idx + num_bytes &amp;gt; curlen) before each memcpy. Since num_bytes is u8,
it is always &amp;gt;= 0, so this strictly subsumes the simpler idx &amp;gt; curlen
form and no separate step is needed.&lt;/p&gt;
&lt;p&gt;[added missing fixes tag]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68279</guid>
    </item>
  </channel>
</rss>
