mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jules Maselbas <jmaselbas@kalray.eu>
To: Sascha Hauer <sha@pengutronix.de>
Cc: Neeraj Pal <neerajpal09@gmail.com>, barebox@lists.infradead.org
Subject: Re: [BUG] Out of bound read of size 1 in __d_alloc function which further leads to __default_memcpy function
Date: Mon, 10 May 2021 12:18:08 +0200	[thread overview]
Message-ID: <20210510101742.GA20010@tellis.lin.mbt.kalray.eu> (raw)
In-Reply-To: <20210507105830.GW19819@pengutronix.de>

Hi,

On Fri, May 07, 2021 at 12:58:30PM +0200, Sascha Hauer wrote:
> Hi,
> 
> On Sun, Apr 18, 2021 at 01:10:10AM +0530, Neeraj Pal wrote:
> > Hi,
> > 
> > I have found the Out of bound read issue of size 1 when argv[2] is "" in
> > __d_alloc function fs/fs.c:1254 which further goes
> > and crashes into  __default_memcpy call lib/string.c:562
> > 
> > Tested on:
> > - barebox-2021.04.0
> > - git commit af0f068a6edad45b033e772056ac0352e1ba3613
> 
> I can reproduce this here. Thanks for reporting it. I just sent out a
> series fixing this issue, you are on Cc:
I think this should also be fixed by the patch I've sent:
(74946415a "fs: Fix link_path_walk to return -ENOENT on empty path")

This patch might not have fixed this exact case when running the nfs
command. Have you been able to repoduce this issue with this patch
applied ?

I've havn't tried to setup a net interface to debug nfs commandi,
instead I was using simpler command such as `md5sum ""`.

Best,
Jules


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


  reply	other threads:[~2021-05-10 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-17 19:40 Neeraj Pal
2021-05-07 10:58 ` Sascha Hauer
2021-05-10 10:18   ` Jules Maselbas [this message]
2021-05-11  8:00     ` Sascha Hauer
2021-05-11  8:52       ` Jules Maselbas

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=20210510101742.GA20010@tellis.lin.mbt.kalray.eu \
    --to=jmaselbas@kalray.eu \
    --cc=barebox@lists.infradead.org \
    --cc=neerajpal09@gmail.com \
    --cc=sha@pengutronix.de \
    /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