From: Dan Carpenter <dan.carpenter@linaro.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
David Lechner <dlechner@baylibre.com>,
Enric Balletbo i Serra <eballetbo@kernel.org>,
Erick Archer <erick.archer@outlook.com>,
Guenter Roeck <linux@roeck-us.net>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
Kees Cook <kees@kernel.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linux-watchdog@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>
Subject: [PATCH 0/3] ihex: add some bounds checking to firmware parsing
Date: Wed, 28 May 2025 23:22:09 +0300 [thread overview]
Message-ID: <cover.1748463049.git.dan.carpenter@linaro.org> (raw)
These three patches go to different subsystems so hopefully the
individual maintainers can apply them. I can resend them as
individual patches if that's easier.
The ihex firmware code is a list of records of various lengths. The
ihex code ensures that total length of the records doesn't read
beyond the end of the fw->data[], however the parsers need to check
that individual records are not too large.
Dan Carpenter (3):
media: gspca: Add bounds checking to firmware parser
watchdog: ziirave_wdt: check record length in ziirave_firm_verify()
Input: ims-pcu - Check record size in ims_pcu_flash_firmware()
drivers/input/misc/ims-pcu.c | 6 ++++++
drivers/media/usb/gspca/vicam.c | 10 ++++++++--
drivers/watchdog/ziirave_wdt.c | 3 +++
3 files changed, 17 insertions(+), 2 deletions(-)
--
2.47.2
next reply other threads:[~2025-05-28 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 20:22 Dan Carpenter [this message]
2025-05-28 20:22 ` [PATCH 3/3] Input: ims-pcu - Check record size in ims_pcu_flash_firmware() Dan Carpenter
2025-05-28 23:26 ` Kees Cook
2025-06-02 11:00 ` Dan Carpenter
2025-05-30 23:14 ` Dmitry Torokhov
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=cover.1748463049.git.dan.carpenter@linaro.org \
--to=dan.carpenter@linaro.org \
--cc=dlechner@baylibre.com \
--cc=dmitry.torokhov@gmail.com \
--cc=eballetbo@kernel.org \
--cc=erick.archer@outlook.com \
--cc=gustavoars@kernel.org \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=javier.carrasco.cruz@gmail.com \
--cc=kees@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mchehab@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=wim@linux-watchdog.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).