From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: abdelrahmanyossef12@gmail.com,
Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH v4] common: buffer access out-of-bounds
Date: Fri, 18 Oct 2024 18:52:48 +0200 [thread overview]
Message-ID: <46f7ed30-f14d-4753-bb42-71eee9cff4a3@pengutronix.de> (raw)
In-Reply-To: <20241018-overflow-v4-1-b0aed7711dc6@gmail.com>
On 18.10.24 18:24, Abdelrahman Youssef via B4 Relay wrote:
> From: Abdelrahman Youssef <abdelrahmanyossef12@gmail.com>
>
> in file_detect_type() to detect file of type socfpga_xload you need at least
> 68 bytes bytes, so we need to check if we have enough bufsize.
> So I moved it after checking if `bufsize >= 256`.
>
> Signed-off-by: Abdelrahman Youssef <abdelrahmanyossef12@gmail.com>
Reviewed-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> This patch is a replacement of the last one because there were some issues with it
As mentioned in the v3 feedback, it's customary to write a changelog here.
Cheers,
Ahmad
> ---
> To: Sascha Hauer <s.hauer@pengutronix.de>
> To: open list:BAREBOX <barebox@lists.infradead.org>
> Signed-off-by: Abdelrahman Youssef <abdelrahmanyossef12@gmail.com>
> ---
> common/filetype.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/common/filetype.c b/common/filetype.c
> index 3690d4ae07..67ae4916d1 100644
> --- a/common/filetype.c
> +++ b/common/filetype.c
> @@ -374,9 +374,6 @@ enum filetype file_detect_type(const void *_buf, size_t bufsize)
> if (le32_to_cpu(buf[5]) == 0x504d5453)
> return filetype_mxs_bootstream;
>
> - if (buf[16] == 0x31305341)
> - return filetype_socfpga_xload;
> -
> if (is_barebox_arm_head(_buf))
> return filetype_arm_barebox;
> if (buf[9] == 0x016f2818 || buf[9] == 0x18286f01)
> @@ -388,6 +385,9 @@ enum filetype file_detect_type(const void *_buf, size_t bufsize)
> if (bufsize < 256)
> return filetype_unknown;
>
> + if (buf[16] == 0x31305341)
> + return filetype_socfpga_xload;
> +
> if (strncmp(buf8, "STM\x32", 4) == 0) {
> if (buf8[74] == 0x01) {
> switch(le32_to_cpu(buf[63])) {
>
> ---
> base-commit: 9d47ff66c3892c5a6ddd4704993365a797fbeb68
> change-id: 20241018-overflow-dc42def7e4f6
>
> Best regards,
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2024-10-18 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 16:24 Abdelrahman Youssef via B4 Relay
2024-10-18 16:52 ` Ahmad Fatoum [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=46f7ed30-f14d-4753-bb42-71eee9cff4a3@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=abdelrahmanyossef12@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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