From: Jonathan Cameron <jic23@kernel.org>
To: Dheeraj Reddy Jonnalagadda <dheeraj.linuxdev@gmail.com>
Cc: lars@metafoo.de, jstephan@baylibre.com, yasin.lee.x@gmail.com,
dan.carpenter@linaro.org, nuno.sa@analog.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH iio-next] iio: proximity: Fix use-after-free in hx9023s_send_cfg()
Date: Sat, 18 Jan 2025 17:21:01 +0000 [thread overview]
Message-ID: <20250118172101.009fe63a@jic23-huawei> (raw)
In-Reply-To: <20250112115314.2e5ad298@jic23-huawei>
On Sun, 12 Jan 2025 11:53:14 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> On Tue, 7 Jan 2025 18:05:10 +0530
> Dheeraj Reddy Jonnalagadda <dheeraj.linuxdev@gmail.com> wrote:
>
> > Reorder the assignment of fw_size to happen before release_firmware()
> > to avoid accessing the firmware structure after it's been freed.
> >
> > Fixes: e9ed97be4fcc ("iio: proximity: hx9023s: Added firmware file parsing functionality")
> > Closes: https://scan7.scan.coverity.com/#/project-view/52337/11354?selectedIssue=1602791
> > Signed-off-by: Dheeraj Reddy Jonnalagadda <dheeraj.linuxdev@gmail.com>
> Gah. I didn't see this until after I'd sent the pull request.
> Never mind, we have plenty of time to get this in during the rc1 cycles.
>
> I'll queue it up after rc1.
>
> Thanks,
>
> Jonathan
I've now queued it but on a fixes tree I can't push out just
yet because it will make a mess of linux-next (it is ahead
of some trees that come later in the merge order for next).
Anyhow, that will all resolve during the merge window and I'll rebase
on rc1.
Thanks,
Jonathan
>
> > ---
> > drivers/iio/proximity/hx9023s.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/iio/proximity/hx9023s.c b/drivers/iio/proximity/hx9023s.c
> > index e092a935dbac..5aa8e5a22f32 100644
> > --- a/drivers/iio/proximity/hx9023s.c
> > +++ b/drivers/iio/proximity/hx9023s.c
> > @@ -1036,12 +1036,13 @@ static int hx9023s_send_cfg(const struct firmware *fw, struct hx9023s_data *data
> > return -ENOMEM;
> >
> > memcpy(bin->data, fw->data, fw->size);
> > - release_firmware(fw);
> >
> > bin->fw_size = fw->size;
> > bin->fw_ver = bin->data[FW_VER_OFFSET];
> > bin->reg_count = get_unaligned_le16(bin->data + FW_REG_CNT_OFFSET);
> >
> > + release_firmware(fw);
> > +
> > return hx9023s_bin_load(data, bin);
> > }
> >
>
>
prev parent reply other threads:[~2025-01-18 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 12:35 [PATCH iio-next] iio: proximity: Fix use-after-free in hx9023s_send_cfg() Dheeraj Reddy Jonnalagadda
2025-01-07 16:42 ` David Lechner
2025-01-12 11:53 ` Jonathan Cameron
2025-01-18 17:21 ` Jonathan Cameron [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=20250118172101.009fe63a@jic23-huawei \
--to=jic23@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=dheeraj.linuxdev@gmail.com \
--cc=jstephan@baylibre.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=yasin.lee.x@gmail.com \
/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