From: tomas <tomasbortoli@gmail.com>
To: raven@themaw.net, autofs@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, syzkaller@googlegroups.com
Subject: [PATCH upstream] KASAN: slab-out-of-bounds Read in getname_kernel
Date: Mon, 2 Jul 2018 00:04:10 +0200 [thread overview]
Message-ID: <38c5a8ad-c192-74b9-b2ff-9eb2a3386930@gmail.com> (raw)
Hi,
I've looked into this issue found by Syzbot and I made a patch:
https://syzkaller.appspot.com/bug?id=d03abd8b42847f7f69b1d1d7f97208ae425b1163
The autofs subsystem does not check that the "path" parameter is present
within the "param" struct passed by the userspace in case the
AUTOFS_DEV_IOCTL_OPENMOUNT_CMD command is passed. Indeed, it assumes a
path is always provided (though a path is not always present, as per how
the struct is defined:
https://github.com/torvalds/linux/blob/master/include/uapi/linux/auto_dev-ioctl.h#L89).
Skipping the check provokes an oob read in "strlen", called by
"getname_kernel", in turn called by the autofs to assess the length of
the non-existing path.
To solve it, modify the "validate_dev_ioctl" function to check also that
a path has been provided if the command is AUTOFS_DEV_IOCTL_OPENMOUNT_CMD.
--- b/fs/autofs/dev-ioctl.c 2018-07-01 23:10:16.059728621 +0200
+++ a/fs/autofs/dev-ioctl.c 2018-07-01 23:10:24.311792133 +0200
@@ -136,6 +136,9 @@ static int validate_dev_ioctl(int cmd, s
goto out;
}
}
+ /* AUTOFS_DEV_IOCTL_OPENMOUNT_CMD without path */
+ else if(_IOC_NR(cmd) == AUTOFS_DEV_IOCTL_OPENMOUNT_CMD)
+ return -EINVAL;
err = 0;
out:
Tested and solves the issue on Linus' main git tree.
Tomas
next reply other threads:[~2018-07-01 22:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 22:04 tomas [this message]
2018-07-02 1:10 ` Ian Kent
2018-07-02 1:42 ` Ian Kent
2018-07-02 8:31 ` tomas
2018-07-02 10:20 ` Ian Kent
2018-07-02 11:55 ` tomas
2018-07-02 12:15 ` Dmitry Vyukov
2018-07-03 1:34 ` Ian Kent
2018-07-03 5:48 ` Dmitry Vyukov
2018-07-03 6:40 ` Ian Kent
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=38c5a8ad-c192-74b9-b2ff-9eb2a3386930@gmail.com \
--to=tomasbortoli@gmail.com \
--cc=autofs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=syzkaller@googlegroups.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
Powered by JetHome