[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166180063676.3312920.11804502368990110703.b4-ty@chromium.org>
Date: Mon, 29 Aug 2022 12:17:19 -0700
From: Kees Cook <keescook@...omium.org>
To: luto@...capital.net, kuniyu@...zon.com, wad@...omium.org
Cc: Kees Cook <keescook@...omium.org>, linux-kernel@...r.kernel.org,
ayudutta@...zon.com, brauner@...nel.org, kuni1840@...il.com,
syzbot+ab17848fe269b573eb71@...kaller.appspotmail.com
Subject: Re: [PATCH v3] seccomp: Move copy_seccomp() to no failure path.
On Tue, 23 Aug 2022 08:45:32 -0700, Kuniyuki Iwashima wrote:
> Our syzbot instance reported memory leaks in do_seccomp() [0], similar
> to the report [1]. It shows that we miss freeing struct seccomp_filter
> and some objects included in it.
>
> We can reproduce the issue with the program below [2] which calls one
> seccomp() and two clone() syscalls.
>
> [...]
Applied to for-linus/seccomp, thanks!
[1/1] seccomp: Move copy_seccomp() to no failure path.
https://git.kernel.org/kees/c/6d17452707ca
--
Kees Cook
Powered by blists - more mailing lists