[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201007061659.GA21685@infradead.org>
Date: Wed, 7 Oct 2020 07:16:59 +0100
From: Christoph Hellwig <hch@...radead.org>
To: Jann Horn <jannh@...gle.com>
Cc: Khalid Aziz <khalid.aziz@...cle.com>,
"David S. Miller" <davem@...emloft.net>,
sparclinux@...r.kernel.org, Linux-MM <linux-mm@...ck.org>,
Khalid Aziz <khalid@...ehiking.org>,
kernel list <linux-kernel@...r.kernel.org>,
Anthony Yznaga <anthony.yznaga@...cle.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: SPARC version of arch_validate_prot() looks broken (UAF read)
On Wed, Oct 07, 2020 at 02:45:39AM +0200, Jann Horn wrote:
> > I think arch_validate_prot() is still the right hook to validate the
> > protection bits. sparc_validate_prot() can iterate over VMAs with read
> > lock. This will, of course, require range as well to be passed to
> > arch_validate_prot().
>
> In that case, do you want to implement this?
Any reason to not just call arch_validate_prot after taking the mmap
lock?
Powered by blists - more mailing lists