From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "José Expósito" <jose.exposito89@gmail.com>
Cc: nick@shmanahar.org, rydberg@bitmath.org,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: atmel_mxt_ts - fix double free in mxt_read_info_block
Date: Sun, 12 Dec 2021 21:02:45 -0800 [thread overview]
Message-ID: <YbbT9fXEk3rMwF6Q@google.com> (raw)
In-Reply-To: <20211212194257.68879-1-jose.exposito89@gmail.com>
On Sun, Dec 12, 2021 at 08:42:57PM +0100, José Expósito wrote:
> The "id_buf" buffer is stored in "data->raw_info_block" and freed by
> "mxt_free_object_table" in case of error.
>
> Return instead of jumping to avoid a double free.
>
> Addresses-Coverity-ID: 1474582 ("Double free")
> Signed-off-by: José Expósito <jose.exposito89@gmail.com>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2021-12-13 5:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 19:42 [PATCH] Input: atmel_mxt_ts - fix double free in mxt_read_info_block José Expósito
2021-12-13 5:02 ` Dmitry Torokhov [this message]
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=YbbT9fXEk3rMwF6Q@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=jose.exposito89@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@shmanahar.org \
--cc=rydberg@bitmath.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).