From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master 3/3] of: fdt: harden against corrupted reserve map entries
Date: Wed, 17 Jul 2024 09:29:13 +0200 [thread overview]
Message-ID: <20240717072913.2830995-3-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20240717072913.2830995-1-a.fatoum@pengutronix.de>
It's only safe to dereference r when dt_ptr_ok(fdt, r) determines that
the r object is within the bounds of fdt.
Commit 8a6b7db572c7 ("of: fdt: fix possibles overflows during
parsing of invalid DTs") had a first attempt at enforcing this, but
failed to do this for the very last element, so shift around the code,
so we only every dereference r when it's safe to do so.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
drivers/of/fdt.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
index 8dca41990c87..f56f5802bb73 100644
--- a/drivers/of/fdt.c
+++ b/drivers/of/fdt.c
@@ -69,14 +69,14 @@ static int of_reservemap_num_entries(const struct fdt_header *fdt)
r = (void *)fdt + be32_to_cpu(fdt->off_mem_rsvmap);
- while (dt_ptr_ok(fdt, r) && r->size) {
+ while (dt_ptr_ok(fdt, r) && n < OF_MAX_RESERVE_MAP) {
+ if (!r->size)
+ return n;
n++;
r++;
- if (n == OF_MAX_RESERVE_MAP)
- return -EINVAL;
}
- return r->size == 0 ? n : -ESPIPE;
+ return n == OF_MAX_RESERVE_MAP ? -EINVAL : -ESPIPE;
}
/**
--
2.39.2
next prev parent reply other threads:[~2024-07-17 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 7:29 [PATCH master 1/3] environment: don't leak environment path buffer Ahmad Fatoum
2024-07-17 7:29 ` [PATCH master 2/3] partition: fix use of uninitialized variable in error message Ahmad Fatoum
2024-07-17 7:29 ` Ahmad Fatoum [this message]
2024-07-19 6:45 ` [PATCH master 1/3] environment: don't leak environment path buffer 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=20240717072913.2830995-3-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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