[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEjxPJ6O3HZ_xdGDvuvYiUNqiPxqvo37V7d5ckLpDM=qF426tw@mail.gmail.com>
Date: Wed, 10 Jun 2020 18:06:50 -0400
From: Stephen Smalley <stephen.smalley.work@...il.com>
To: trix@...hat.com
Cc: Paul Moore <paul@...l-moore.com>,
Eric Paris <eparis@...isplace.org>,
Ondrej Mosnacek <omosnace@...hat.com>,
Jeffrey Vander Stoep <jeffv@...gle.com>, rgb@...hat.com,
SElinux list <selinux@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/1] selinux: fix double free
On Wed, Jun 10, 2020 at 5:57 PM <trix@...hat.com> wrote:
>
> From: Tom Rix <trix@...hat.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@...hat.com>
Acked-by: Stephen Smalley <stephen.smalley.work@...il.com>
Powered by blists - more mailing lists