From: jwcart2 <jwcart2@tycho.nsa.gov>
To: Nicolas Iooss <nicolas.iooss@m4x.org>,
Petr Lautrbach <plautrba@redhat.com>
Cc: selinux@vger.kernel.org
Subject: Re: [Non-DoD Source] Re: [PATCH 1/3] libsepol: Fix RESOURCE_LEAK defects reported by coverity scan
Date: Fri, 1 Feb 2019 13:19:22 -0500 [thread overview]
Message-ID: <28fe4f11-54ad-830c-ea95-2656b1e5569d@tycho.nsa.gov> (raw)
In-Reply-To: <CAJfZ7=mK=okzh1S8_1h6_TPRMTXEUQyHUccTf-Uai=Az8SDRQg@mail.gmail.com>
On 1/31/19 4:17 PM, Nicolas Iooss wrote:
> On Thu, Jan 31, 2019 at 2:22 PM Petr Lautrbach <plautrba@redhat.com> wrote:
>>
>> Signed-off-by: Petr Lautrbach <plautrba@redhat.com>
>> ---
>> libsepol/cil/src/cil_binary.c | 12 ++++++++++++
>> libsepol/cil/src/cil_resolve_ast.c | 10 ++++++++++
>> libsepol/cil/src/cil_symtab.c | 1 +
>> libsepol/src/expand.c | 3 +++
>> libsepol/src/kernel_to_cil.c | 2 ++
>> libsepol/src/kernel_to_conf.c | 2 ++
>> 6 files changed, 30 insertions(+)
>>
>> diff --git a/libsepol/cil/src/cil_binary.c b/libsepol/cil/src/cil_binary.c
>> index 0cc6eeb1..a645c95d 100644
>> --- a/libsepol/cil/src/cil_binary.c
>> +++ b/libsepol/cil/src/cil_binary.c
>> @@ -912,6 +912,8 @@ int cil_sensalias_to_policydb(policydb_t *pdb, struct cil_alias *cil_alias)
>> key = cil_strdup(cil_alias->datum.fqn);
>> rc = symtab_insert(pdb, SYM_LEVELS, key, sepol_alias, SCOPE_DECL, 0, NULL);
>> if (rc != SEPOL_OK) {
>> + if (rc == 1)
>> + free(sepol_alias);
>> goto exit;
>> }
>
> There is something weird here. The exit label starts with
> "level_datum_destroy(sepol_alias);". This is not a serious issue
> because level_datum_destroy() does not do anything, but after this
> patch, cil_sensalias_to_policydb()'s code seems to use sepol_alias
> after freeing it.
>
> Should the call to level_datum_destroy(sepol_alias) be removed, or
> moved before free(sepol_alias)?
>
The real problem is the statement after the "level_datum_destroy(sepol_alias);".
The "free(sepol_level);" should be "free(sepol_alias);".
The sepol_level references a datum passed back by hashtab_search() in
__cil_get_sepol_class_datum() and is not a new object.
Jim
> Thanks,
> Nicolas
>
>
--
James Carter <jwcart2@tycho.nsa.gov>
National Security Agency
next prev parent reply other threads:[~2019-02-01 18:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 13:22 [PATCH 1/3] libsepol: Fix RESOURCE_LEAK defects reported by coverity scan Petr Lautrbach
2019-01-31 13:22 ` [PATCH 2/3] libselinux: " Petr Lautrbach
2019-01-31 21:47 ` Nicolas Iooss
2019-02-06 20:33 ` [PATCH v2] " Petr Lautrbach
2019-02-06 22:40 ` Nicolas Iooss
2019-02-10 18:32 ` Nicolas Iooss
2019-01-31 13:22 ` [PATCH 3/3] libsemanage: Fix USE_AFTER_FREE " Petr Lautrbach
2019-01-31 21:57 ` Nicolas Iooss
2019-02-01 12:45 ` Petr Lautrbach
2019-01-31 21:17 ` [PATCH 1/3] libsepol: Fix RESOURCE_LEAK " Nicolas Iooss
2019-02-01 18:19 ` jwcart2 [this message]
2019-01-31 21:33 ` Nicolas Iooss
2019-02-01 19:32 ` [Non-DoD Source] " jwcart2
2019-02-01 20:07 ` [Non-DoD Source] " jwcart2
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28fe4f11-54ad-830c-ea95-2656b1e5569d@tycho.nsa.gov \
--to=jwcart2@tycho.nsa.gov \
--cc=nicolas.iooss@m4x.org \
--cc=plautrba@redhat.com \
--cc=selinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).