From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Sang-Heon Jeon <ekffu200098@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] tools/bootconfig: Fix integer overflow in size check
Date: Thu, 10 Sep 2026 09:34:22 +0900 [thread overview]
Message-ID: <20260910093422.e24e680b0506c16af51b2bbd@kernel.org> (raw)
In-Reply-To: <178900024679.183840.10345859264677533824.stgit@devnote2>
On Thu, 10 Sep 2026 09:30:46 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> Sashiko reported that on 32-bit systems, if the size in the bootconfig
> footer is corrupted such that adding BOOTCONFIG_FOOTER_SIZE wraps
> around (for instance, if size is 0xFFFFFFFF), the size check in
> load_xbc_from_initrd() can be bypassed:
>
> if (stat.st_size < size + BOOTCONFIG_FOOTER_SIZE) {
> pr_err("bootconfig size is too big\n");
> return -E2BIG;
> }
>
> This would lead to load_xbc_fd() being called with a negative size,
> resulting in an undersized allocation, heap overflow on read, and
> out-of-bounds write on the terminating null byte.
>
> Avoid the integer overflow by checking whether size is greater than
> stat.st_size - BOOTCONFIG_FOOTER_SIZE. Since stat.st_size is already
> verified to be at least BOOTCONFIG_FOOTER_SIZE earlier in the function,
> this subtraction will never underflow.
>
> Fixes: 950313ebf79c ("tools: bootconfig: Add bootconfig command")
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Closes: https://lore.kernel.org/all/20260909161113.16C691F00A3A@smtp.kernel.org/
> Assisted-by: Antigravity:gemini-3.8-flash
OOps, I forgot to add:
Cc: stable@vger.kernel.org
Thanks,
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> ---
> tools/bootconfig/main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/bootconfig/main.c b/tools/bootconfig/main.c
> index 7dc9fff9b637..b380ad6777fa 100644
> --- a/tools/bootconfig/main.c
> +++ b/tools/bootconfig/main.c
> @@ -218,7 +218,7 @@ static int load_xbc_from_initrd(int fd, char **buf)
> csum = le32toh(csum);
>
> /* Wrong size error */
> - if (stat.st_size < size + BOOTCONFIG_FOOTER_SIZE) {
> + if (size > stat.st_size - BOOTCONFIG_FOOTER_SIZE) {
> pr_err("bootconfig size is too big\n");
> return -E2BIG;
> }
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2026-09-10 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 0:30 Masami Hiramatsu (Google)
2026-09-10 0:34 ` Masami Hiramatsu [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=20260910093422.e24e680b0506c16af51b2bbd@kernel.org \
--to=mhiramat@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ekffu200098@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=stable@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®