From: Kees Cook <keescook@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, Dmitry Vyukov <dvyukov@google.com>
Subject: [PATCH] fs: make sure we do not read beyond allocation
Date: Thu, 3 Oct 2013 09:34:11 -0700 [thread overview]
Message-ID: <20131003163411.GA17101@www.outflux.net> (raw)
In dentry_string_cmp (via__d_lookup_rcu), when CONFIG_DCACHE_WORD_ACCESS
is set, word-width memory reads are performed. However, the string
allocation size may not be a multiple of the word size. To avoid reading
past the end of such an allocation, we must allocate in multiples of
the word size.
Found by the Kernel Address Sanitizer project:
https://code.google.com/p/address-sanitizer/wiki/AddressSanitizerForKernel
Reported-by: Dmitry Vyukov <dvyukov@google.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
---
fs/dcache.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/fs/dcache.c b/fs/dcache.c
index 4100030..23665e2 100644
--- a/fs/dcache.c
+++ b/fs/dcache.c
@@ -1570,7 +1570,11 @@ struct dentry *__d_alloc(struct super_block *sb, const struct qstr *name)
*/
dentry->d_iname[DNAME_INLINE_LEN-1] = 0;
if (name->len > DNAME_INLINE_LEN-1) {
- dname = kmalloc(name->len + 1, GFP_KERNEL);
+ size_t alloc_size = name->len + 1;
+#ifdef CONFIG_DCACHE_WORD_ACCESS
+ alloc_size = round_up(alloc_size, sizeof(unsigned long));
+#endif
+ dname = kmalloc(alloc_size, GFP_KERNEL);
if (!dname) {
kmem_cache_free(dentry_cache, dentry);
return NULL;
--
1.7.9.5
--
Kees Cook
Chrome OS Security
next reply other threads:[~2013-10-03 16:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 16:34 Kees Cook [this message]
2013-10-03 17:58 ` [PATCH] fs: make sure we do not read beyond allocation Al Viro
2013-10-03 18:03 ` Kees Cook
2013-10-03 18:23 ` Al Viro
2013-10-03 19:36 ` Kees Cook
2013-10-03 20:57 ` Al Viro
2013-10-03 21:30 ` Kees Cook
2013-10-04 6:05 ` Dmitry Vyukov
2013-10-04 10:38 ` Richard Weinberger
2013-10-04 10:53 ` Dmitry Vyukov
2013-10-04 13:53 ` Richard Weinberger
2013-10-11 11:26 ` Dmitry Vyukov
2013-10-11 11:27 ` Dmitry Vyukov
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=20131003163411.GA17101@www.outflux.net \
--to=keescook@chromium.org \
--cc=dvyukov@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).