From: Yufen Yu <yuyufen@huawei.com>
To: <gregkh@linuxfoundation.org>, <linux-kernel@vger.kernel.org>
Cc: <rafael@kernel.org>, <axboe@kernel.dk>, <hch@lst.de>,
<linux-block@vger.kernel.org>
Subject: [PATCH] drivers core: don't do anything in device_del() when device_add() fail
Date: Thu, 1 Apr 2021 09:01:38 -0400 [thread overview]
Message-ID: <20210401130138.2164928-1-yuyufen@huawei.com> (raw)
Recently, our syzbot test reported NULL pointer dereference in
device_del() by injecting memory allocation fail in device_add().
For now, callers of device_add(), such as add_disk(), may ignore
device_add()'s fail and go on working. In unregister path, it will
call device_del() from del_gendisk(). That can cause various NULL
pointer dereference, including dev->p is NULL in kill_device(),
'name' is NULL in sysfs_remove_link(), kobj->sd is 'NULL' when call
dpm_sysfs_remove(), and so on.
To avoid these kernel panic, we call device_del() only when device_add()
is success.
Signed-off-by: Yufen Yu <yuyufen@huawei.com>
---
drivers/base/core.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index f29839382f81..a10ec5dbc577 100644
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -3380,6 +3380,9 @@ void device_del(struct device *dev)
struct class_interface *class_intf;
unsigned int noio_flag;
+ if (!dev->p)
+ return;
+
device_lock(dev);
kill_device(dev);
device_unlock(dev);
--
2.25.4
next reply other threads:[~2021-04-01 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 13:01 Yufen Yu [this message]
2021-04-01 13:31 ` [PATCH] drivers core: don't do anything in device_del() when device_add() fail Rafael J. Wysocki
2021-04-02 15:06 ` Greg KH
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=20210401130138.2164928-1-yuyufen@huawei.com \
--to=yuyufen@huawei.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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: 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;
as well as URLs for NNTP newsgroup(s).