From: Sreeraj S Kurup <sreekuttan2156239@gmail.com>
To: o-takashi@sakamocchi.jp
Cc: linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Sreeraj S Kurup <sreekuttan2156239@gmail.com>
Subject: [PATCH V3 v3 2/2] firewire: core: validate sub-block lengths in fw_core_add_descriptor()
Date: Sat, 25 Jul 2026 15:52:55 +0000 [thread overview]
Message-ID: <20260725155255.3054-3-sreekuttan2156239@gmail.com> (raw)
In-Reply-To: <20260725155255.3054-1-sreekuttan2156239@gmail.com>
When traversing internal block structures of a descriptor in
fw_core_add_descriptor(), each sub-block header specifies its own length
in the upper 16 bits of its header quadlet.
If a malformed or corrupted descriptor provides a sub-block length that
exceeds the remaining total length of the descriptor buffer, the parsing
loop advances past the allocated boundary of desc->data, leading to an
out-of-bounds read access.
Validate each sub-block's length against the remaining descriptor size
before advancing the offset pointer to ensure loop bounds safety.
Signed-off-by: Sreeraj S Kurup <sreekuttan2156239@gmail.com>
---
drivers/firewire/core-card.c | 20 ++++++++++++++++++--
1 file changed, 18 insertions(+), 2 deletions(-)
diff --git a/drivers/firewire/core-card.c b/drivers/firewire/core-card.c
index eaec54ea287a..7b5d324aa7cc 100644
--- a/drivers/firewire/core-card.c
+++ b/drivers/firewire/core-card.c
@@ -173,9 +173,25 @@ int fw_core_add_descriptor(struct fw_descriptor *desc)
return -EINVAL;
i = 0;
- while (i < desc->length)
- i += (desc->data[i] >> 16) + 1;
+ /*
+ * Validate internal block structures within the descriptor. Each sub-block
+ * encodes its length in the top 16 bits of its header quadlet.
+ */
+ while (i < desc->length) {
+ u16 block_len = desc->data[i] >> 16;
+
+ /*
+ * Guard against corrupted descriptors where an individual block length
+ * claims to extend past the allocated end of desc->data, avoiding
+ * out-of-bounds reads.
+ */
+ if (block_len >= desc->length - i)
+ return -EINVAL;
+
+ i += block_len + 1;
+ }
+ /* The sum of sub-block lengths must match total descriptor length */
if (i != desc->length)
return -EINVAL;
--
2.54.0
next prev parent reply other threads:[~2026-07-25 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 15:52 [PATCH v3 0/2] firewire: core: validate descriptor and " Sreeraj S Kurup
2026-07-25 15:52 ` [PATCH V3 v3 1/2] firewire: core: validate overall descriptor length " Sreeraj S Kurup
2026-07-25 15:52 ` Sreeraj S Kurup [this message]
2026-07-27 0:47 ` [PATCH v3 0/2] firewire: core: validate descriptor and sub-block lengths " Takashi Sakamoto
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=20260725155255.3054-3-sreekuttan2156239@gmail.com \
--to=sreekuttan2156239@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=o-takashi@sakamocchi.jp \
/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®