[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHC9VhR0-814-YsC3ugTsCzL1be37tyxZHTs7Dq2mY+iC8pjgA@mail.gmail.com>
Date: Mon, 13 Jun 2022 16:34:10 -0400
From: Paul Moore <paul@...l-moore.com>
To: Xiu Jianfeng <xiujianfeng@...wei.com>
Cc: stephen.smalley.work@...il.com, eparis@...isplace.org,
cgzones@...glemail.com, omosnace@...hat.com,
michalorzel.eng@...il.com, austin.kim@....com,
selinux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next] selinux: Fix memleak in security_read_state_kernel
On Mon, Jun 13, 2022 at 10:01 AM Xiu Jianfeng <xiujianfeng@...wei.com> wrote:
>
> In this function, it directly returns the result of __security_read_policy
> without freeing the allocated memory in *data, cause memory leak issue,
> so free the memory if __security_read_policy failed.
>
> Signed-off-by: Xiu Jianfeng <xiujianfeng@...wei.com>
> ---
> security/selinux/ss/services.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
Merged into selinux/next, thanks.
--
paul-moore.com
Powered by blists - more mailing lists