diff options
| author | Vlad Tsyrklevich <vlad@tsyrklevich.net> | 2019-01-11 14:34:38 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-01-22 21:40:34 +0100 |
| commit | 4190c5fd8a7f370513f4215ee617203a7d75cc57 (patch) | |
| tree | b19514d8c11581e84650b045d66d0d0b3c91f91f /drivers/media/platform | |
| parent | 328f3de2ef766cc27f9a85b20691493642a51417 (diff) | |
| download | talos-obmc-linux-4190c5fd8a7f370513f4215ee617203a7d75cc57.tar.gz talos-obmc-linux-4190c5fd8a7f370513f4215ee617203a7d75cc57.zip | |
omap2fb: Fix stack memory disclosure
commit a01421e4484327fe44f8e126793ed5a48a221e24 upstream.
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: b39a982ddecf ("OMAP: DSS2: omapfb driver")
Cc: security@kernel.org
[b.zolnierkie: prefix patch subject with "omap2fb: "]
Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/media/platform')
0 files changed, 0 insertions, 0 deletions
