[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <166812034327.20280.16820301693244403901.b4-ty@rivosinc.com>
Date: Thu, 10 Nov 2022 14:45:43 -0800
From: Palmer Dabbelt <palmer@...osinc.com>
To: Jisheng Zhang <jszhang@...nel.org>, Guo Ren <guoren@...nel.org>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>
Cc: linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org
Subject: Re: [PATCH] riscv: process: fix kernel info leakage
On Sat, 29 Oct 2022 19:34:50 +0800, Jisheng Zhang wrote:
> thread_struct's s[12] may contain random kernel memory content, which
> may be finally leaked to userspace. This is a security hole. Fix it
> by clearing the s[12] array in thread_struct when fork.
>
> As for kthread case, it's better to clear the s[12] array as well.
>
>
> [...]
Applied, thanks!
[1/1] riscv: process: fix kernel info leakage
https://git.kernel.org/palmer/c/6510c78490c4
Best regards,
--
Palmer Dabbelt <palmer@...osinc.com>
Powered by blists - more mailing lists