From: Wenjia Zhao <driverfuzzing@gmail.com> To: unlisted-recipients:; (no To-header on input) Cc: driverfuzzing@gmail.com, Florian Tobias Schandinat <FlorianSchandinat@gmx.de>, Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: [PATCH 3/3] video: fbdev: fix the out-of-bounds access cr_data->bak Date: Mon, 1 Feb 2021 09:56:34 -0600 [thread overview] Message-ID: <1612194994-50994-1-git-send-email-driverfuzzing@gmail.com> (raw) The size of cr_data->bak is CURSOR_SIZE/4, however the access size in the is CURSOR_SIZE in the loop. It causes the out-of-bounds access. Signed-off-by: Wenjia Zhao <driverfuzzing@gmail.com> --- drivers/video/fbdev/via/viafbdev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/video/fbdev/via/viafbdev.c b/drivers/video/fbdev/via/viafbdev.c index 22deb34..ef217cc 100644 --- a/drivers/video/fbdev/via/viafbdev.c +++ b/drivers/video/fbdev/via/viafbdev.c @@ -839,7 +839,7 @@ static int viafb_cursor(struct fb_info *info, struct fb_cursor *cursor) if (cursor->set & FB_CUR_SETSHAPE) { struct { u8 data[CURSOR_SIZE]; - u32 bak[CURSOR_SIZE / 4]; + u32 bak[CURSOR_SIZE]; } *cr_data = kzalloc(sizeof(*cr_data), GFP_ATOMIC); int size = ((cursor->image.width + 7) >> 3) * cursor->image.height; -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Wenjia Zhao <driverfuzzing@gmail.com> Cc: linux-fbdev@vger.kernel.org, driverfuzzing@gmail.com, Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, Florian Tobias Schandinat <FlorianSchandinat@gmx.de>, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org Subject: [PATCH 3/3] video: fbdev: fix the out-of-bounds access cr_data->bak Date: Mon, 1 Feb 2021 09:56:34 -0600 [thread overview] Message-ID: <1612194994-50994-1-git-send-email-driverfuzzing@gmail.com> (raw) The size of cr_data->bak is CURSOR_SIZE/4, however the access size in the is CURSOR_SIZE in the loop. It causes the out-of-bounds access. Signed-off-by: Wenjia Zhao <driverfuzzing@gmail.com> --- drivers/video/fbdev/via/viafbdev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/video/fbdev/via/viafbdev.c b/drivers/video/fbdev/via/viafbdev.c index 22deb34..ef217cc 100644 --- a/drivers/video/fbdev/via/viafbdev.c +++ b/drivers/video/fbdev/via/viafbdev.c @@ -839,7 +839,7 @@ static int viafb_cursor(struct fb_info *info, struct fb_cursor *cursor) if (cursor->set & FB_CUR_SETSHAPE) { struct { u8 data[CURSOR_SIZE]; - u32 bak[CURSOR_SIZE / 4]; + u32 bak[CURSOR_SIZE]; } *cr_data = kzalloc(sizeof(*cr_data), GFP_ATOMIC); int size = ((cursor->image.width + 7) >> 3) * cursor->image.height; -- 2.7.4 _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2021-02-01 15:57 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-01 15:56 Wenjia Zhao [this message] 2021-02-01 15:56 ` [PATCH 3/3] video: fbdev: fix the out-of-bounds access cr_data->bak Wenjia Zhao
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1612194994-50994-1-git-send-email-driverfuzzing@gmail.com \ --to=driverfuzzing@gmail.com \ --cc=FlorianSchandinat@gmx.de \ --cc=b.zolnierkie@samsung.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=linux-fbdev@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.