From: Greg KH <gregkh@linuxfoundation.org>
To: syzbot <syzbot+92f32d4e21fb246d31a2@syzkaller.appspotmail.com>
Cc: andriy.shevchenko@linux.intel.com, asierra@xes-inc.com,
corbet@lwn.net, ext-kimmo.rautkoski@vaisala.com, jslaby@suse.com,
kai.heng.feng@canonical.com, linux-api@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, mika.westerberg@linux.intel.com,
paulburton@kernel.org, peter@hurleysoftware.com, sr@denx.de,
syzkaller-bugs@googlegroups.com, yamada.masahiro@socionext.com,
yegorslists@googlemail.com
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in mem16_serial_out
Date: Thu, 12 Dec 2019 11:57:54 +0100 [thread overview]
Message-ID: <20191212105754.GC1476206@kroah.com> (raw)
In-Reply-To: <00000000000003cc8505994f9036@google.com>
On Mon, Dec 09, 2019 at 05:38:01PM -0800, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit bd94c4077a0b2ecc35562c294f80f3659ecd8499
> Author: Masahiro Yamada <yamada.masahiro@socionext.com>
> Date: Wed Oct 28 03:46:05 2015 +0000
>
> serial: support 16-bit register interface for console
That would be because that is when this function was added to the kernel
:)
Again, you are asking the kernel to write to a bad place in memory, and
then crash when that happens. That sounds like the correct
functionality to me...
thanks,
greg k-h
next prev parent reply other threads:[~2019-12-12 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 19:35 BUG: unable to handle kernel NULL pointer dereference in mem16_serial_out syzbot
2019-12-10 1:38 ` syzbot
2019-12-12 10:57 ` Greg KH [this message]
2019-12-13 9:05 ` Dmitry Vyukov
2021-04-26 16:14 ` [PATCH] serial: 8250: fix NULL pointer dereference in serial8250_do_startup() Vegard Nossum
2021-04-26 16:17 ` Greg Kroah-Hartman
2021-04-26 16:33 ` Vegard Nossum
2021-04-28 6:36 ` BUG: unable to handle kernel NULL pointer dereference in mem16_serial_out syzbot
2021-05-13 14:24 ` [PATCH] serial: 8250: fix NULL pointer dereference in serial8250_do_startup() Greg Kroah-Hartman
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=20191212105754.GC1476206@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=asierra@xes-inc.com \
--cc=corbet@lwn.net \
--cc=ext-kimmo.rautkoski@vaisala.com \
--cc=jslaby@suse.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=paulburton@kernel.org \
--cc=peter@hurleysoftware.com \
--cc=sr@denx.de \
--cc=syzbot+92f32d4e21fb246d31a2@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yamada.masahiro@socionext.com \
--cc=yegorslists@googlemail.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