public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH v2 0/1] selinux: fix double free
@ 2020-06-10 21:57 trix
  2020-06-10 21:57 ` [PATCH v2 1/1] " trix
  0 siblings, 1 reply; 4+ messages in thread
From: trix @ 2020-06-10 21:57 UTC (permalink / raw)
  To: paul, stephen.smalley.work, eparis, omosnace, jeffv, rgb
  Cc: selinux, linux-kernel, Tom Rix

From: Tom Rix <trix@redhat.com>

repo: linux-next
tag: next-20200610

Running clang scan-view over linux-next uncovers many problem only a
few are memory related, this one looked like the most serious.

Changes from v1

Fix call to kfree
-		kfree(names);
+		kfree(*names);


Tom Rix (1):
  selinux: fix double free

 security/selinux/ss/services.c | 4 ++++
 1 file changed, 4 insertions(+)

-- 
2.18.1


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [PATCH v2 1/1] selinux: fix double free
  2020-06-10 21:57 [PATCH v2 0/1] selinux: fix double free trix
@ 2020-06-10 21:57 ` trix
  2020-06-10 22:06   ` Stephen Smalley
  2020-06-11  2:13   ` Paul Moore
  0 siblings, 2 replies; 4+ messages in thread
From: trix @ 2020-06-10 21:57 UTC (permalink / raw)
  To: paul, stephen.smalley.work, eparis, omosnace, jeffv, rgb
  Cc: selinux, linux-kernel, Tom Rix

From: Tom Rix <trix@redhat.com>

Clang's static analysis tool reports these double free memory errors.

security/selinux/ss/services.c:2987:4: warning: Attempt to free released memory [unix.Malloc]
                        kfree(bnames[i]);
                        ^~~~~~~~~~~~~~~~
security/selinux/ss/services.c:2990:2: warning: Attempt to free released memory [unix.Malloc]
        kfree(bvalues);
        ^~~~~~~~~~~~~~

So improve the security_get_bools error handling by freeing these variables
and setting their return pointers to NULL and the return len to 0

Signed-off-by: Tom Rix <trix@redhat.com>
---
 security/selinux/ss/services.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/security/selinux/ss/services.c b/security/selinux/ss/services.c
index 313919bd42f8..ef0afd878bfc 100644
--- a/security/selinux/ss/services.c
+++ b/security/selinux/ss/services.c
@@ -2888,8 +2888,12 @@ int security_get_bools(struct selinux_state *state,
 	if (*names) {
 		for (i = 0; i < *len; i++)
 			kfree((*names)[i]);
+		kfree(*names);
 	}
 	kfree(*values);
+	*len = 0;
+	*names = NULL;
+	*values = NULL;
 	goto out;
 }
 
-- 
2.18.1


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH v2 1/1] selinux: fix double free
  2020-06-10 21:57 ` [PATCH v2 1/1] " trix
@ 2020-06-10 22:06   ` Stephen Smalley
  2020-06-11  2:13   ` Paul Moore
  1 sibling, 0 replies; 4+ messages in thread
From: Stephen Smalley @ 2020-06-10 22:06 UTC (permalink / raw)
  To: trix
  Cc: Paul Moore, Eric Paris, Ondrej Mosnacek, Jeffrey Vander Stoep,
	rgb, SElinux list, linux-kernel

On Wed, Jun 10, 2020 at 5:57 PM <trix@redhat.com> wrote:
>
> From: Tom Rix <trix@redhat.com>
>
> Clang's static analysis tool reports these double free memory errors.
>
> security/selinux/ss/services.c:2987:4: warning: Attempt to free released memory [unix.Malloc]
>                         kfree(bnames[i]);
>                         ^~~~~~~~~~~~~~~~
> security/selinux/ss/services.c:2990:2: warning: Attempt to free released memory [unix.Malloc]
>         kfree(bvalues);
>         ^~~~~~~~~~~~~~
>
> So improve the security_get_bools error handling by freeing these variables
> and setting their return pointers to NULL and the return len to 0
>
> Signed-off-by: Tom Rix <trix@redhat.com>

Acked-by: Stephen Smalley <stephen.smalley.work@gmail.com>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH v2 1/1] selinux: fix double free
  2020-06-10 21:57 ` [PATCH v2 1/1] " trix
  2020-06-10 22:06   ` Stephen Smalley
@ 2020-06-11  2:13   ` Paul Moore
  1 sibling, 0 replies; 4+ messages in thread
From: Paul Moore @ 2020-06-11  2:13 UTC (permalink / raw)
  To: trix
  Cc: Stephen Smalley, Eric Paris, Ondrej Mosnacek, jeffv, rgb, selinux,
	linux-kernel

On Wed, Jun 10, 2020 at 5:57 PM <trix@redhat.com> wrote:
> From: Tom Rix <trix@redhat.com>
>
> Clang's static analysis tool reports these double free memory errors.
>
> security/selinux/ss/services.c:2987:4: warning: Attempt to free released memory [unix.Malloc]
>                         kfree(bnames[i]);
>                         ^~~~~~~~~~~~~~~~
> security/selinux/ss/services.c:2990:2: warning: Attempt to free released memory [unix.Malloc]
>         kfree(bvalues);
>         ^~~~~~~~~~~~~~
>
> So improve the security_get_bools error handling by freeing these variables
> and setting their return pointers to NULL and the return len to 0
>
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
>  security/selinux/ss/services.c | 4 ++++
>  1 file changed, 4 insertions(+)

Thanks Tom for the patch and Stephen for the review.

I've marked this for stable and merged it into selinux/stable-5.8.
Considering we are just a few days away from the close of the merge
window and -rc1, I'll probably hold off until next to send this up to
Linus.

> diff --git a/security/selinux/ss/services.c b/security/selinux/ss/services.c
> index 313919bd42f8..ef0afd878bfc 100644
> --- a/security/selinux/ss/services.c
> +++ b/security/selinux/ss/services.c
> @@ -2888,8 +2888,12 @@ int security_get_bools(struct selinux_state *state,
>         if (*names) {
>                 for (i = 0; i < *len; i++)
>                         kfree((*names)[i]);
> +               kfree(*names);
>         }
>         kfree(*values);
> +       *len = 0;
> +       *names = NULL;
> +       *values = NULL;
>         goto out;
>  }
>
> --
> 2.18.1

-- 
paul moore
www.paul-moore.com

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2020-06-11  2:13 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-06-10 21:57 [PATCH v2 0/1] selinux: fix double free trix
2020-06-10 21:57 ` [PATCH v2 1/1] " trix
2020-06-10 22:06   ` Stephen Smalley
2020-06-11  2:13   ` Paul Moore

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox