From: Delene Tchio Romuald <delenetchior1@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Delene Tchio Romuald <delenetchior1@gmail.com>,
stable@vger.kernel.org
Subject: [PATCH] staging: greybus: fix size_t underflow in cap_get_ims_certificate()
Date: Sun, 5 Apr 2026 00:22:42 +0100 [thread overview]
Message-ID: <20260404232242.68423-1-delenetchior1@gmail.com> (raw)
In cap_get_ims_certificate(), the certificate size is computed as:
*size = op->response->payload_size - sizeof(*response);
Both operands are size_t (unsigned), so if a malformed Greybus module
sends a response with payload_size smaller than sizeof(*response),
the subtraction wraps to a very large value. The subsequent memcpy()
then causes a heap buffer overflow.
Add a payload size validation before the subtraction to ensure the
response is large enough to contain the fixed-size response header.
Cc: stable@vger.kernel.org
Signed-off-by: Delene Tchio Romuald <delenetchior1@gmail.com>
---
drivers/staging/greybus/authentication.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/staging/greybus/authentication.c b/drivers/staging/greybus/authentication.c
index 97b9937bb..1c14ad184 100644
--- a/drivers/staging/greybus/authentication.c
+++ b/drivers/staging/greybus/authentication.c
@@ -132,6 +132,12 @@ static int cap_get_ims_certificate(struct gb_cap *cap, u32 class, u32 id,
response = op->response->payload;
*result = response->result_code;
+
+ if (op->response->payload_size < sizeof(*response)) {
+ ret = -EINVAL;
+ goto done;
+ }
+
*size = op->response->payload_size - sizeof(*response);
memcpy(certificate, response->certificate, *size);
--
2.43.0
next reply other threads:[~2026-04-04 23:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 23:22 Delene Tchio Romuald [this message]
2026-04-05 8:00 ` [PATCH] staging: greybus: fix size_t underflow in cap_get_ims_certificate() Greg KH
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=20260404232242.68423-1-delenetchior1@gmail.com \
--to=delenetchior1@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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