[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABRcYmJgOAFMO2Uuyn1sdoTLk1PXrxuqo4Hwkg6UkSDgMOvnYg@mail.gmail.com>
Date: Tue, 4 Jul 2023 17:45:53 +0200
From: Florent Revest <revest@...omium.org>
To: linux-kernel@...r.kernel.org, linux-mm@...ck.org
Cc: akpm@...ux-foundation.org, catalin.marinas@....com,
anshuman.khandual@....com, joey.gouly@....com, mhocko@...e.com,
keescook@...omium.org, david@...hat.com, peterx@...hat.com,
izbyshev@...ras.ru, broonie@...nel.org, szabolcs.nagy@....com,
kpsingh@...nel.org, gthelen@...gle.com, toiwoton@...il.com,
linux-stable@...r.kernel.org
Subject: Re: [PATCH v3 3/5] mm: Make PR_MDWE_REFUSE_EXEC_GAIN an unsigned long
On Tue, Jul 4, 2023 at 5:37 PM Florent Revest <revest@...omium.org> wrote:
>
> Defining a prctl flag as an int is a footgun because on a 64 bit machine
> and with a variadic implementation of prctl (like in musl and glibc),
> when used directly as a prctl argument, it can get casted to long with
> garbage upper bits which would result in unexpected behaviors.
>
> This patch changes the constant to an unsigned long to eliminate that
> possibilities. This does not break UAPI.
>
> Fixes: b507808ebce2 ("mm: implement memory-deny-write-execute as a prctl")
> Cc: linux-stable@...r.kernel.org
Oops, this was supposed to be stable@...r.kernel.org... I'll fix that
tag as part of v4.
Powered by blists - more mailing lists