/fs/minix/

.15.y'>linux-2.6.15.y Linux kernel stable treeStable Group
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDouglas Anderson <dianders@chromium.org>2021-10-05 19:29:08 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-10-20 11:45:05 +0200
commita7b45024f66f9ec769e8dbb1a51ae83cd05929c7 (patch)
tree69b078302340bfe23d66f70bce011aec40166bab
parentd0f0e17103972f40b46930afcb7685438028ec0d (diff)
downloadlinux-a7b45024f66f9ec769e8dbb1a51ae83cd05929c7.tar.gz
drm/edid: In connector_bad_edid() cap num_of_ext by num_blocks read
commit 97794170b696856483f74b47bfb6049780d2d3a0 upstream. In commit e11f5bd8228f ("drm: Add support for DP 1.4 Compliance edid corruption test") 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. Let's fix this by adding a bounds check. This is important for handling the case where there'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]`. Fixes: e11f5bd8228f ("drm: Add support for DP 1.4 Compliance edid corruption test") Reported-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Signed-off-by: Douglas Anderson <dianders@chromium.org> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20211005192905.v2.1.Ib059f9c23c2611cb5a9d760e7d0a700c1295928d@changeid Signed-off-by: Dave Airlie <airlied@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>