From: Andrew Morton <akpm@linux-foundation.org>
To: Entropy Moe <3ntr0py1337@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: KASAN: stack-out-of-bounds Write in mpol_to_str
Date: Fri, 20 Mar 2020 23:45:13 -0700 [thread overview]
Message-ID: <20200320234513.9b05abe1ade85712db2d6478@linux-foundation.org> (raw)
In-Reply-To: <CALzBtj+8AYASaYW2fqgmgthCgeAJ2N0Q+ey2wqgEKjBtH34Vcg@mail.gmail.com>
On Fri, 20 Mar 2020 12:36:38 +0400 Entropy Moe <3ntr0py1337@gmail.com> wrote:
> Hello Randy,
> please see attached POC for the vulnerability.
>
Thanks. Ouch. afaict shmem's S_IFREG inode's mpol's preferred_node is
messed up.
I don't think anyone has worked on this code in a decade or more. Is
someone up to taking a look please?
> On Mon, Mar 16, 2020 at 10:46 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> > On 3/15/20 12:57 PM, Entropy Moe wrote:
> > > Hello team,
> > > how are you ?
> > > I wanted to report a bug on mempolicy.c. I found the bug on the latest
> > version of the kernel.
> > >
> > > which is stack out of bound vulnerability.
> > >
> > > I am attaching report.
> > >
> > > If you need the POC crash code, I can provide.
> >
> > Hi Moe,
> >
> > Please post the POC code and your kernel .config file.
> >
> > thanks.
> > --
> > ~Randy
> >
> >
next prev parent reply other threads:[~2020-03-21 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALzBtjLSqFhSNAf4YusxuE1piUTzOSLFGFD4RrhPLQAmgpyL5g@mail.gmail.com>
2020-03-16 18:46 ` KASAN: stack-out-of-bounds Write in mpol_to_str Randy Dunlap
[not found] ` <CALzBtj+8AYASaYW2fqgmgthCgeAJ2N0Q+ey2wqgEKjBtH34Vcg@mail.gmail.com>
2020-03-21 6:45 ` Andrew Morton [this message]
2020-03-26 0:54 ` Randy Dunlap
2020-03-26 0:45 ` [PATCH] mm: mempolicy: require at least one nodeid for MPOL_PREFERRED Randy Dunlap
2020-03-26 2:23 KASAN: stack-out-of-bounds Write in mpol_to_str syzbot
2020-03-26 3:47 ` Randy Dunlap
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=20200320234513.9b05abe1ade85712db2d6478@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=3ntr0py1337@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.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).