https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 03:18:10 +0000 https://cve.radiocsirt.org/vuln/cve-2021-47444 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/edid: In connector_bad_edid() cap num_of_ext by num_blocks read</p> <p>In commit e11f5bd8228f (&#34;drm: Add support for DP 1.4 Compliance edid corruption test&#34;) the function connector_bad_edid() started assuming that the memory for the EDID passed to it was big enough to hold `edid[0x7e] + 1` blocks of data (1 extra for the base block). It completely ignored the fact that the function was passed `num_blocks` which indicated how much memory had been allocated for the EDID.</p> <p>Let&#39;s fix this by adding a bounds check.</p> <p>This is important for handling the case where there&#39;s an error in the first block of the EDID. In that case we will call connector_bad_edid() without having re-allocated memory based on `edid[0x7e]`.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/edid: In connector_bad_edid() cap num_of_ext by num_blocks read</p> <p>In commit e11f5bd8228f (&#34;drm: Add support for DP 1.4 Compliance edid corruption test&#34;) the function connector_bad_edid() started assuming that the memory for the EDID passed to it was big enough to hold `edid[0x7e] + 1` blocks of data (1 extra for the base block). It completely ignored the fact that the function was passed `num_blocks` which indicated how much memory had been allocated for the EDID.</p> <p>Let&#39;s fix this by adding a bounds check.</p> <p>This is important for handling the case where there&#39;s an error in the first block of the EDID. In that case we will call connector_bad_edid() without having re-allocated memory based on `edid[0x7e]`.</p> https://cve.radiocsirt.org/vuln/cve-2021-47444