mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kenneth Kabogo <kennethkabogo2@gmail.com>
To: andersson@kernel.org, konradybcio@kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Kenneth Kabogo <kennethkabogo2@gmail.com>
Subject: [PATCH] soc: qcom: mdt_loader: fix off-by-one heap overflow in segment name
Date: Sat, 12 Sep 2026 09:56:51 +0300	[thread overview]
Message-ID: <20260912065651.59968-1-kennethkabogo2@gmail.com> (raw)

mdt_load_split_segment() builds a segment firmware filename by
overwriting the last three characters of a kstrdup'd copy of fw_name
with "b%02d" formatted from segment. %02d is a minimum field width,
not a cap: for segment in [0, 99] this produces exactly "bNN" + NUL,
which fits the buffer, but for segment >= 100 it writes "b100" or
wider, one or more bytes past the end of the kstrdup allocation.

segment is not bounded to [0, 99] anywhere before this point. It is a
raw index into the firmware's ELF program header table, ultimately
bounded only by e_phnum, a 16-bit ELF field (max 65535). The existing
check in mdt_header_valid() only verifies that the program header
table fits inside the firmware file, not that e_phnum itself is sane,
so a small firmware file can supply e_phnum > 100 and reach this path
with segment >= 100 from either qcom_mdt_read_metadata() (the hash
segment scan) or the main loadable-segment loop in
qcom_mdt_load_no_init(), whenever the image uses the split-firmware
convention.

segment was never valid past 99 under this driver's own "bNN" naming
scheme, so reject it outright instead of widening the buffer.

Found by code inspection while auditing the Qualcomm PIL/PAS
firmware-authentication flow. No reproducer beyond code inspection is
available; I don't have affected hardware to trigger it on.

Signed-off-by: Kenneth Kabogo <kennethkabogo2@gmail.com>
---
 drivers/soc/qcom/mdt_loader.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/soc/qcom/mdt_loader.c b/drivers/soc/qcom/mdt_loader.c
index 002100fe2..0d55e9e0a 100644
--- a/drivers/soc/qcom/mdt_loader.c
+++ b/drivers/soc/qcom/mdt_loader.c
@@ -77,6 +77,9 @@ static ssize_t mdt_load_split_segment(void *ptr, const struct elf32_phdr *phdrs,
 	if (strlen(fw_name) < 4)
 		return -EINVAL;
 
+	if (segment > 99)
+		return -EINVAL;
+
 	char *seg_name __free(kfree) = kstrdup(fw_name, GFP_KERNEL);
 	if (!seg_name)
 		return -ENOMEM;
-- 
2.55.0


                 reply	other threads:[~2026-09-12  6:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260912065651.59968-1-kennethkabogo2@gmail.com \
    --to=kennethkabogo2@gmail.com \
    --cc=andersson@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@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®