From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeff LaBundy <jeff@labundy.com>
Subject: Re: [PATCH] Input: iqs5xx: validate firmware record destination span
Date: Fri, 24 Jul 2026 16:59:39 -0700 [thread overview]
Message-ID: <amP8Z3TxA-BJq9QO@google.com> (raw)
In-Reply-To: <20260715083850.32155-1-pengpeng@iscas.ac.cn>
On Wed, Jul 15, 2026 at 04:38:50PM +0800, Pengpeng Hou wrote:
> The firmware record parser checks that the record address starts within
> the programmable map, but does not check that the complete record data
> fits in that map. A record near the end of the map can therefore make
> the copy to pmap exceed its destination span.
>
> Check the record length against the remaining programmable map range
> before copying the record data.
>
> Fixes: 7b5bb55d0dad ("Input: add support for Azoteq IQS550/572/525")
> Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2026-07-24 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 8:38 Pengpeng Hou
2026-07-24 23:59 ` 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=amP8Z3TxA-BJq9QO@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=jeff@labundy.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pengpeng@iscas.ac.cn \
/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
all inboxes | Powered by JetHome®