mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Petr Mladek <pmladek@suse.com>, anon anon <742991625abc@gmail.com>
Cc: wangkefeng.wang@huawei.com, sergey.senozhatsky@gmail.com,
	syzkaller@googlegroups.com, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Subject: Re: KASAN: slab-out-of-bounds Write in vgacon_scroll
Date: Tue, 28 Jan 2020 15:58:04 +0100	[thread overview]
Message-ID: <4ab69855-6112-52f4-bee2-3358664d0c20@samsung.com> (raw)
In-Reply-To: <20200128124912.chttagasucdpydhk@pathway.suse.cz>


On 1/28/20 1:49 PM, Petr Mladek wrote:
> On Tue 2020-01-28 18:23:46, anon anon wrote:
>> Dear Linux kernel developers,
>>
>> I found the crash "KASAN: slab-out-of-bounds Write in vgacon_scroll"
>> when running syzkaller, hope it's unknown:
>>
>> Linux version: Linux v4.17-rc4 (75bc37fefc44)
>> Branch: master
>>
>> This crash still exists on the latest linux kernel Linux v5.5-rc6.
>> Please get C repo and crash log generated by syzkaller, as well as the
>> .config I used for linux kernel from the attachment. Thanks.
> 
> The out-of-bound access seems to be in vgacon_scroll() and thus
> in vgacon code.
> 
> Unfortunately, most people in CC are printk-guys. They were mentioned
> by ./scripts/get_maintainer.pl -f drivers/video/console/vgacon.c
> just because the very last comment (tree wide pr_warning() clean up).
> 
> Bartolomej seems to be the only relevant name.
> 
> Bartolomej,
> 
> are you going to look at it? Or should we add more people or some list

Help is welcomed as I'm not going to look at it in the foreseeable future
(I'm busy enough with other things).

> (dri-devel@lists.freedesktop.org or linux-fbdev@vger.kernel.org) into CC?

Added to Cc:, thanks.

> Thanks,
> Petr

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics

  reply	other threads:[~2020-01-28 14:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA=061EoW8AmjUrBLsJy5nTDz-1jeArLeB+z6HJuyZud0zZXug@mail.gmail.com>
2020-01-28 12:49 ` Petr Mladek
2020-01-28 14:58   ` Bartlomiej Zolnierkiewicz [this message]
2020-01-29 14:15     ` Sergey Senozhatsky
2020-01-29 14:17       ` Sergey Senozhatsky
2020-01-29 14:40         ` Sergey Senozhatsky
2020-01-29 14:59           ` Dmitry Vyukov
2020-01-29 15:06             ` Dmitry Vyukov
2020-01-29 17:34               ` Tetsuo Handa

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=4ab69855-6112-52f4-bee2-3358664d0c20@samsung.com \
    --to=b.zolnierkie@samsung.com \
    --cc=742991625abc@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=syzkaller@googlegroups.com \
    --cc=wangkefeng.wang@huawei.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®