From: Sreeraj S Kurup <sreekuttan2156239@gmail.com>
To: o-takashi@sakamocchi.jp
Cc: linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
sreekuttan2156239@gmail.com
Subject: [PATCH v2 1/2] firewire: Fix out-of-bounds access in CSR iterator
Date: Tue, 3 Nov 2026 15:14:20 +0000 [thread overview]
Message-ID: <20261103151421.7248-2-sreekuttan2156239@gmail.com> (raw)
In-Reply-To: <20261103151421.7248-1-sreekuttan2156239@gmail.com>
The fw_csr_iterator_next() function reads ci->p before
checking if it has reached the end.
This can cause an out-of-bounds read when the iterator
has no more entries.
Check the iterator position before reading the entry.
Move the pointer forward only after reading a valid entry.
Signed-off-by: Sreeraj S Kurup <sreekuttan2156239@gmail.com>
---
drivers/firewire/core-device.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/firewire/core-device.c b/drivers/firewire/core-device.c
index a68100d3da0b..36667841ca3c 100644
--- a/drivers/firewire/core-device.c
+++ b/drivers/firewire/core-device.c
@@ -40,10 +40,14 @@ EXPORT_SYMBOL(fw_csr_iterator_init);
int fw_csr_iterator_next(struct fw_csr_iterator *ci, int *key, int *value)
{
+ if (ci->p >= ci->end)
+ return 0;
+
*key = *ci->p >> 24;
*value = *ci->p & 0xffffff;
- return ci->p++ < ci->end;
+ ci->p++;
+ return 1;
}
EXPORT_SYMBOL(fw_csr_iterator_next);
--
2.55.0
next prev parent reply other threads:[~2026-11-03 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 6:53 [PATCH] " Sreeraj S Kurup
2026-11-03 4:24 ` Takashi Sakamoto
2026-11-03 15:14 ` [PATCH v2 0/2] " Sreeraj S Kurup
2026-11-03 15:14 ` Sreeraj S Kurup [this message]
2026-11-03 15:14 ` [PATCH v2 2/2] firewire: Add KUnit tests for " Sreeraj S Kurup
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=20261103151421.7248-2-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®