From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Abdelrahman Youssef <abdelrahmanyossef12@gmail.com>,
s.hauer@pengutronix.de
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v4] of: fdt: fix possible overflow during parsing of fdt
Date: Fri, 15 Nov 2024 21:15:45 +0100 [thread overview]
Message-ID: <a4c698d8-3279-471d-9476-652e9580b8c2@pengutronix.de> (raw)
In-Reply-To: <20241114155115.594121-1-abdelrahmanyossef12@gmail.com>
On 14.11.24 16:51, Abdelrahman Youssef wrote:
> While fuzzing, the name marked by FDT_BEGIN_NODE sometimes extends beyond
> the struct block area, causing a heap-overflow.
>
> Since `maxlen` is an unsigned integer representing the length of name,
> It can be negative, so it overflows to large numbers, Causing strnlen()
> to overflow.
>
> So we can just change the type of maxlen to signed and check if it's a
> non-positive value, because name has a minimum length of 1 byte ('\0').
>
> Also in strnlen() we shouldn't check for bytes exceeding maxlen, so we can remove
> + 1 in strnlen(). We also change if (len > maxlen) to >= to count for the null
> terminator.
>
> Signed-off-by: Abdelrahman Youssef <abdelrahmanyossef12@gmail.com>
Reviewed-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>
> ---
> v3 -> v4:
> - replace maxlen < 0 to maxlen <= 0 (Sascha)
> - remove + 1 in strnlen() (Sascha)
> v2 -> v3
> - changed formatting
> v1 -> v2
> - the overflow was due to integer overflow not out-of-bounds (Ahmad)
> ---
> drivers/of/fdt.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
> index 2c3ea31394..75af1844f3 100644
> --- a/drivers/of/fdt.c
> +++ b/drivers/of/fdt.c
> @@ -176,7 +176,7 @@ static struct device_node *__of_unflatten_dtb(const void *infdt, int size,
> void *dt_strings;
> struct fdt_header f;
> int ret;
> - unsigned int maxlen;
> + int maxlen;
> const struct fdt_header *fdt = infdt;
>
> ret = fdt_parse_header(infdt, size, &f);
> @@ -210,8 +210,13 @@ static struct device_node *__of_unflatten_dtb(const void *infdt, int size,
> maxlen = (unsigned long)fdt + f.off_dt_struct +
> f.size_dt_struct - (unsigned long)name;
>
> - len = strnlen(name, maxlen + 1);
> - if (len > maxlen) {
> + if (maxlen <= 0) {
> + ret = -ESPIPE;
> + goto err;
> + }
> +
> + len = strnlen(name, maxlen);
> + if (len >= maxlen) {
> ret = -ESPIPE;
> goto err;
> }
--
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 |
next prev parent reply other threads:[~2024-11-15 20:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 15:51 Abdelrahman Youssef
2024-11-14 16:39 ` Jules Maselbas
[not found] ` <CABwgSGY3SQGUoc3xY9XVX3aHwRV6s5xFuKABtgCf0vT26-1=_Q@mail.gmail.com>
[not found] ` <CABwgSGYcFoMncRWoyOjG19K2GiuMjrEomNGvG3E2fEX3wiM=RA@mail.gmail.com>
2024-11-14 17:50 ` AbdelRahman Yossef
2024-11-15 20:15 ` Ahmad Fatoum [this message]
2024-11-25 10:23 ` Sascha Hauer
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=a4c698d8-3279-471d-9476-652e9580b8c2@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