summaryrefslogtreecommitdiffstats
path: root/drivers/video
diff options
context:
space:
mode:
authorWei Chen <harperchen1110@gmail.com>2023-03-07 13:08:56 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2023-04-06 12:10:40 +0200
commitb8b7d5eac5ee984e42424de776ec1e04d1cc2f89 (patch)
treebecbf4361ba6faa4fc62fc63dc67a9fca462a12a /drivers/video
parent32854bc91ae7debcdefdc7ae881ed83385a04792 (diff)
downloadlinux-stable-b8b7d5eac5ee984e42424de776ec1e04d1cc2f89.tar.gz
linux-stable-b8b7d5eac5ee984e42424de776ec1e04d1cc2f89.tar.bz2
linux-stable-b8b7d5eac5ee984e42424de776ec1e04d1cc2f89.zip
fbdev: tgafb: Fix potential divide by zero
[ Upstream commit f90bd245de82c095187d8c2cabb8b488a39eaecc ] fb_set_var would by called when user invokes ioctl with cmd FBIOPUT_VSCREENINFO. User-provided data would finally reach tgafb_check_var. In case var->pixclock is assigned to zero, divide by zero would occur when checking whether reciprocal of var->pixclock is too high. Similar crashes have happened in other fbdev drivers. There is no check and modification on var->pixclock along the call chain to tgafb_check_var. We believe it could also be triggered in driver tgafb from user site. Signed-off-by: Wei Chen <harperchen1110@gmail.com> Signed-off-by: Helge Deller <deller@gmx.de> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/video')
-rw-r--r--drivers/video/fbdev/tgafb.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/drivers/video/fbdev/tgafb.c b/drivers/video/fbdev/tgafb.c
index 251dbd282f5e..84d5daef9766 100644
--- a/drivers/video/fbdev/tgafb.c
+++ b/drivers/video/fbdev/tgafb.c
@@ -173,6 +173,9 @@ tgafb_check_var(struct fb_var_screeninfo *var, struct fb_info *info)
{
struct tga_par *par = (struct tga_par *)info->par;
+ if (!var->pixclock)
+ return -EINVAL;
+
if (par->tga_type == TGA_TYPE_8PLANE) {
if (var->bits_per_pixel != 8)
return -EINVAL;