From: Helge Deller <deller@gmx.de>
To: Albin Babu Varghese <albinbabuvarghese20@gmail.com>,
Simona Vetter <simona@ffwll.ch>
Cc: syzbot+48b0652a95834717f190@syzkaller.appspotmail.com,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds
Date: Tue, 30 Sep 2025 22:46:23 +0200 [thread overview]
Message-ID: <cb00a5e2-6e50-4b01-bcd7-33eeae57ed63@gmx.de> (raw)
In-Reply-To: <20250927075010.119671-1-albinbabuvarghese20@gmail.com>
On 9/27/25 09:50, Albin Babu Varghese wrote:
> KASAN reports vmalloc-out-of-bounds writes in sys_imageblit during console
> resize operations. The crash happens when bit_putcs renders characters
> outside the allocated framebuffer region.
>
> Call trace: vc_do_resize -> clear_selection -> invert_screen ->
> do_update_region -> fbcon_putcs -> bit_putcs -> sys_imageblit
>
> The console resize changes dimensions but bit_putcs doesn't validate that
> the character positions fit within the framebuffer before rendering.
> This causes writes past the allocated buffer in fb_imageblit functions.
>
> Fix by checking bounds before rendering:
> - Return if dy + height > yres (would write past bottom)
> - Break if dx + width > xres (would write past right edge)
>
> Reported-by: syzbot+48b0652a95834717f190@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=48b0652a95834717f190
> Tested-by: syzbot+48b0652a95834717f190@syzkaller.appspotmail.com
> Signed-off-by: Albin Babu Varghese <albinbabuvarghese20@gmail.com>
> ---
> drivers/video/fbdev/core/bitblit.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/video/fbdev/core/bitblit.c b/drivers/video/fbdev/core/bitblit.c
> index f9475c14f733..4c732284384a 100644
> --- a/drivers/video/fbdev/core/bitblit.c
> +++ b/drivers/video/fbdev/core/bitblit.c
> @@ -160,6 +160,9 @@ static void bit_putcs(struct vc_data *vc, struct fb_info *info,
> image.height = vc->vc_font.height;
> image.depth = 1;
>
> + if (image.dy + image.height > info->var.yres)
> + return;
> +
I wonder if the image.height value should be capped in this case,
instead of not rendering any chars at all?
Something like (untested!):
+ if (image.dy >= info->var.yres)
+ return;
+ image.height = min(image.height, info->var.yres - image.dy);
> if (attribute) {
> buf = kmalloc(cellsize, GFP_ATOMIC);
> if (!buf)
> @@ -173,6 +176,10 @@ static void bit_putcs(struct vc_data *vc, struct fb_info *info,
> cnt = count;
>
> image.width = vc->vc_font.width * cnt;
> +
> + if (image.dx + image.width > info->var.xres)
> + break;
> +
same here.
> pitch = DIV_ROUND_UP(image.width, 8) + scan_align;
> pitch &= ~scan_align;
> size = pitch * image.height + buf_align;
next prev parent reply other threads:[~2025-09-30 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-27 7:50 [PATCH] fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds Albin Babu Varghese
2025-09-30 20:46 ` Helge Deller [this message]
2025-10-01 17:19 ` Albin Babu Varghese
2025-10-01 18:36 ` Helge Deller
2025-10-02 8:52 ` Albin Babu Varghese
2025-10-02 10:11 ` Helge Deller
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=cb00a5e2-6e50-4b01-bcd7-33eeae57ed63@gmx.de \
--to=deller@gmx.de \
--cc=albinbabuvarghese20@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=syzbot+48b0652a95834717f190@syzkaller.appspotmail.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox