From: Jiri Slaby <jirislaby@kernel.org>
To: Yang Yingliang <yangyingliang@huawei.com>, b.zolnierkie@samsung.com
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, 张云海 <zhangyunhai@nsfocus.com>
Subject: Re: [PATCH] vgacon: Fix an out-of-bounds in vgacon_scrollback_update()
Date: Thu, 30 Jul 2020 15:38:06 +0200 [thread overview]
Message-ID: <9aecd7ac-5060-6b8d-61f8-393431eb243f@kernel.org> (raw)
In-Reply-To: <c3714d73-d5fe-c77a-e554-bb1ff4fd6980@huawei.com>
On 30. 07. 20, 15:24, Yang Yingliang wrote:
>
> On 2020/7/30 19:04, Jiri Slaby wrote:
>> On 13. 07. 20, 12:57, Yang Yingliang wrote:
>>> I got a slab-out-of-bounds report when I doing fuzz test.
>>>
>>> [ 334.989515]
>>> ==================================================================
>>> [ 334.989577] BUG: KASAN: slab-out-of-bounds in
>>> vgacon_scroll+0x57a/0x8ed
>>> [ 334.989588] Write of size 1766 at addr ffff8883de69ff3e by task
>>> test/2658
>>> [ 334.989593]
>>> [ 334.989608] CPU: 3 PID: 2658 Comm: test Not tainted
>>> 5.7.0-rc5-00005-g152036d1379f #789
>>> [ 334.989617] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
>>> BIOS rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org 04/01/2014
>>> [ 334.989624] Call Trace:
>>> [ 334.989646] dump_stack+0xe4/0x14e
>>> [ 334.989676] print_address_description.constprop.5+0x3f/0x60
>>> [ 334.989699] ? vgacon_scroll+0x57a/0x8ed
>>> [ 334.989710] __kasan_report.cold.8+0x92/0xaf
>>> [ 334.989735] ? vgacon_scroll+0x57a/0x8ed
>>> [ 334.989761] kasan_report+0x37/0x50
>>> [ 334.989789] check_memory_region+0x1c1/0x1e0
>>> [ 334.989806] memcpy+0x38/0x60
>>> [ 334.989824] vgacon_scroll+0x57a/0x8ed
>>> [ 334.989876] con_scroll+0x4ef/0x5e0
>> ...
>>> Because vgacon_scrollback_cur->tail plus memcpy size is greater than
>>> vgacon_scrollback_cur->size. Fix this by checking the memcpy size.
>>>
>>> Reported-by: Hulk Robot <hulkci@huawei.com>
>>> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
>>> ---
>>> drivers/video/console/vgacon.c | 11 ++++++++---
>>> 1 file changed, 8 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/video/console/vgacon.c
>>> b/drivers/video/console/vgacon.c
>>> index 998b0de1812f..b51ffb9a208d 100644
>>> --- a/drivers/video/console/vgacon.c
>>> +++ b/drivers/video/console/vgacon.c
>>> @@ -243,6 +243,7 @@ static void vgacon_scrollback_startup(void)
>>> static void vgacon_scrollback_update(struct vc_data *c, int t, int
>>> count)
>>> {
>>> void *p;
>>> + int size;
>>> if (!vgacon_scrollback_cur->data ||
>>> !vgacon_scrollback_cur->size ||
>>> c->vc_num != fg_console)
>>> @@ -251,13 +252,17 @@ static void vgacon_scrollback_update(struct
>>> vc_data *c, int t, int count)
>>> p = (void *) (c->vc_origin + t * c->vc_size_row);
>>> while (count--) {
>>> + size = vgacon_scrollback_cur->size -
>>> vgacon_scrollback_cur->tail;
>>> + if (size > c->vc_size_row)
>>> + size = c->vc_size_row;
>>> +
>>> scr_memcpyw(vgacon_scrollback_cur->data +
>>> vgacon_scrollback_cur->tail,
>>> - p, c->vc_size_row);
>>> + p, size);
>> Are you sure the consumer can handle split lines? As vgacon_scrolldelta
>> (soff in particular) looks to me like it doesn't.
>>
>> Have you tested you patch? I mean with soft scrollback on the vga
>> console?
>
> I only test the patch with the reproduce program.
Out of curiosity, what is it doing? Resize and then scroll by \n (line
feed)? Can you share it?
thanks,
--
js
next prev parent reply other threads:[~2020-07-30 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 10:57 Yang Yingliang
2020-07-30 11:04 ` Jiri Slaby
2020-07-30 13:24 ` Yang Yingliang
2020-07-30 13:38 ` Jiri Slaby [this message]
[not found] ` <3df26fed-5ade-df26-6417-380401b9650b@huawei.com>
2020-07-31 4:56 ` Jiri Slaby
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=9aecd7ac-5060-6b8d-61f8-393431eb243f@kernel.org \
--to=jirislaby@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yangyingliang@huawei.com \
--cc=zhangyunhai@nsfocus.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
all inboxes | Powered by JetHome®