From: BluezTestBot <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] efa900: tools: Fix memory leak in hciconfig
Date: Mon, 09 May 2022 13:37:53 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/f0106d-42e9b8@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: efa90050937c5eabc6c70a466bd886f164388484
https://github.com/bluez/bluez/commit/efa90050937c5eabc6c70a466bd886f164388484
Author: Ildar Kamaletdinov <i.kamaletdinov@omp.ru>
Date: 2022-05-09 (Mon, 09 May 2022)
Changed paths:
M tools/hciconfig.c
Log Message:
-----------
tools: Fix memory leak in hciconfig
printf() was using function that return dynamic allocated memory as
a parameter.
Found by Linux Verification Center (linuxtesting.org) with the SVACE
static analysis tool.
Commit: a4741ef4bf6c6fb262b38a897312e929c2161cf9
https://github.com/bluez/bluez/commit/a4741ef4bf6c6fb262b38a897312e929c2161cf9
Author: Ildar Kamaletdinov <i.kamaletdinov@omp.ru>
Date: 2022-05-09 (Mon, 09 May 2022)
Changed paths:
M tools/btgatt-client.c
M tools/btgatt-server.c
Log Message:
-----------
tools: Fix memory leaks in btgatt-server/client
According to man buffer allocated by getline() should be freed by
the user program even if getline() failed.
Found by Linux Verification Center (linuxtesting.org) with the SVACE
static analysis tool.
Commit: e9ec1cf8715d72195a94d748777a19b8e2ba4db5
https://github.com/bluez/bluez/commit/e9ec1cf8715d72195a94d748777a19b8e2ba4db5
Author: Ildar Kamaletdinov <i.kamaletdinov@omp.ru>
Date: 2022-05-09 (Mon, 09 May 2022)
Changed paths:
M tools/rfcomm.c
Log Message:
-----------
tools: Fix handle leak in rfcomm
Some branches of execution can make handle (socket) leakage.
Found by Linux Verification Center (linuxtesting.org) with the SVACE
static analysis tool.
Commit: 42e9b8db92d5d8725e9a1bfd93a5c6a257186776
https://github.com/bluez/bluez/commit/42e9b8db92d5d8725e9a1bfd93a5c6a257186776
Author: Ildar Kamaletdinov <i.kamaletdinov@omp.ru>
Date: 2022-05-09 (Mon, 09 May 2022)
Changed paths:
M src/device.c
Log Message:
-----------
device: Fix uninitialized value usage
Definitely `dbus_bool_t b;` must be initialized before comparing it
with current value.
Found by Linux Verification Center (linuxtesting.org) with the SVACE
static analysis tool.
Compare: https://github.com/bluez/bluez/compare/f0106d92a1e0...42e9b8db92d5
reply other threads:[~2022-05-09 20:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/master/f0106d-42e9b8@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.