From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Atul Akella <atul.akella@gmail.com>
Cc: andersson@kernel.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remoteproc: core: fix integer overflow in rproc_da_to_va() bounds check
Date: Thu, 5 Nov 2026 10:40:00 -0600 [thread overview]
Message-ID: <auyxYDRg1QbIrKNo@p14s> (raw)
In-Reply-To: <20261031161131.1647-1-atul.akella@gmail.com>
On Sat, Oct 31, 2026 at 09:41:30PM +0530, Atul Akella wrote:
> offset is calculated as da - carveout->da and stored in a 32 bit
> signed int, while da and carveout->da are both u64. For a
> sufficiently small da, the 64bit difference is truncated into the
> 32 bit int, bypassing the offset < 0 underflow check with a small
> positive value. Additionally, offset + len > carveout->len can
> itself overflow when offset and len are both large, providing a
> second bypass.
>
> Rewrite the bounds check entirely in u64 arithmetic. Reject
> underflow before computing offset (da < carveout->da). Replace the
> addition-based overflow check with a subtraction-based one
> (len > carveout->len - offset) so no intermediate sum can wrap.
>
> Signed-off-by: Atul Akella <atul.akella@gmail.com>
> ---
> drivers/remoteproc/remoteproc_core.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
Applied.
Thanks,
Mathieu
> diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c
> index 23f8539a99bd..d5fa9d23bd5c 100644
> --- a/drivers/remoteproc/remoteproc_core.c
> +++ b/drivers/remoteproc/remoteproc_core.c
> @@ -198,18 +198,20 @@ void *rproc_da_to_va(struct rproc *rproc, u64 da, size_t len, bool *is_iomem)
> }
>
> list_for_each_entry(carveout, &rproc->carveouts, node) {
> - int offset = da - carveout->da;
> + u64 offset;
>
> /* Verify that carveout is allocated */
> if (!carveout->va)
> continue;
>
> /* try next carveout if da is too small */
> - if (offset < 0)
> + if (da < carveout->da)
> continue;
>
> - /* try next carveout if da is too large */
> - if (offset + len > carveout->len)
> + offset = da - carveout->da;
> +
> + /* try next carveout if da or len is too large */
> + if (offset > carveout->len || len > carveout->len - offset)
> continue;
>
> ptr = carveout->va + offset;
> --
> 2.43.0
>
prev parent reply other threads:[~2026-11-05 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 16:11 Atul Akella
2026-11-05 16:40 ` Mathieu Poirier [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=auyxYDRg1QbIrKNo@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=atul.akella@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.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
all inboxes | Powered by JetHome®