Vlad Tsyrklevich a01421e448 omap2fb: Fix stack memory disclosure ... Using [1] for static analysis I found that the OMAPFB_QUERY_PLANE, OMAPFB_GET_COLOR_KEY, OMAPFB_GET_DISPLAY_INFO, and OMAPFB_GET_VRAM_INFO cases could all leak uninitialized stack memory--either due to uninitialized padding or 'reserved' fields. Fix them by clearing the shared union used to store copied out data. [1] https://github.com/vlad902/kernel-uninitialized-memory-checker Signed-off-by: Vlad Tsyrklevich <vlad@tsyrklevich.net> Reviewed-by: Kees Cook <keescook@chromium.org> Fixes: b39a982dde ("OMAP: DSS2: omapfb driver") Cc: security@kernel.org [b.zolnierkie: prefix patch subject with "omap2fb: "] Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>		2019-01-11 14:34:38 +01:00
..
omapfb	omap2fb: Fix stack memory disclosure	2019-01-11 14:34:38 +01:00
Kconfig	drivers: omap2: Kconfig: make FB_OMAP2_DSS_INIT depend on OF	2018-05-04 08:27:04 -04:00
Makefile	drm/omap: move omapdss & displays under omapdrm	2015-12-29 11:07:48 +02:00