[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHC9VhQdfPBn4kbY0xRPaCvNBJJGdQQe_90A4Hhdsj6gVr6pAQ@mail.gmail.com>
Date: Tue, 14 Jun 2022 22:02:58 -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, austin.kim@....com, omosnace@...hat.com,
michalorzel.eng@...il.com, selinux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next] selinux: Fix memleak in security_read_policy
On Tue, Jun 14, 2022 at 9:25 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(-)
This is another case where there is not actually a memory leak as the
only caller of security_read_policy() is sel_open_policy() which will
free the buffer it passes to security_read_policy() on error.
If you want you could add a comment to security_read_policy()
indicating that the caller is responsible for freeing the memory.
--
paul-moore.com
Powered by blists - more mailing lists