From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Richard Weinberger <richard@nod.at>, <linux-mtd@lists.infradead.org>
Cc: <linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH] ubifs: wbuf: Don't leak kernel memory to flash
Date: Tue, 17 Nov 2020 09:25:08 +0800 [thread overview]
Message-ID: <bfea268f-b5c2-5467-7b17-5eef7b0269ce@huawei.com> (raw)
In-Reply-To: <20201116210530.26230-1-richard@nod.at>
在 2020/11/17 5:05, Richard Weinberger 写道:
> Write buffers use a kmalloc()'ed buffer, they can leak
> up to seven bytes of kernel memory to flash if writes are not
> aligned.
> So use ubifs_pad() to fill these gaps with padding bytes.
> This was never a problem while scanning because the scanner logic
> manually aligns node lengths and skips over these gaps.
>
> Cc: <stable@vger.kernel.org>
> Fixes: 1e51764a3c2ac05a2 ("UBIFS: add new flash file system")
> Signed-off-by: Richard Weinberger <richard@nod.at>
> ---
> fs/ubifs/io.c | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ubifs/io.c b/fs/ubifs/io.c
> index 7e4bfaf2871f..eae9cf5a57b0 100644
> --- a/fs/ubifs/io.c
> +++ b/fs/ubifs/io.c
> @@ -319,7 +319,7 @@ void ubifs_pad(const struct ubifs_info *c, void *buf, int pad)
> {
> uint32_t crc;
>
> - ubifs_assert(c, pad >= 0 && !(pad & 7));
> + ubifs_assert(c, pad >= 0);
>
> if (pad >= UBIFS_PAD_NODE_SZ) {
> struct ubifs_ch *ch = buf;
> @@ -764,6 +764,10 @@ int ubifs_wbuf_write_nolock(struct ubifs_wbuf *wbuf, void *buf, int len)
> * write-buffer.
> */
> memcpy(wbuf->buf + wbuf->used, buf, len);
> + if (aligned_len > len) {
> + ubifs_assert(c, aligned_len - len < 8);
> + ubifs_pad(c, wbuf->buf + wbuf->used + len, aligned_len - len);
> + }
>
> if (aligned_len == wbuf->avail) {
> dbg_io("flush jhead %s wbuf to LEB %d:%d",
> @@ -856,13 +860,18 @@ int ubifs_wbuf_write_nolock(struct ubifs_wbuf *wbuf, void *buf, int len)
> }
>
> spin_lock(&wbuf->lock);
> - if (aligned_len)
> + if (aligned_len) {
> /*
> * And now we have what's left and what does not take whole
> * max. write unit, so write it to the write-buffer and we are
> * done.
> */
> memcpy(wbuf->buf, buf + written, len);
> + if (aligned_len > len) {
> + ubifs_assert(c, aligned_len - len < 8);
> + ubifs_pad(c, wbuf->buf + len, aligned_len - len);
> + }
> + }
>
> if (c->leb_size - wbuf->offs >= c->max_write_size)
> wbuf->size = c->max_write_size;
>
Reviewed-by: Zhihao Cheng <chengzhihao1@huawei.com>
next prev parent reply other threads:[~2020-11-17 1:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 21:05 Richard Weinberger
2020-11-17 1:25 ` Zhihao Cheng [this message]
2020-11-17 8:43 ` Richard Weinberger
2020-11-17 9:21 ` Zhihao Cheng
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=bfea268f-b5c2-5467-7b17-5eef7b0269ce@huawei.com \
--to=chengzhihao1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=stable@vger.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
all inboxes | Powered by JetHome®