mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhao Feng <zhaofeng2@cmss.chinamobile.com>
To: greybus-dev@lists.linaro.org
Cc: johan@kernel.org, elder@kernel.org, gregkh@linuxfoundation.org,
	elder@ieee.org, linux-kernel@vger.kernel.org,
	syzbot+693652ded53d3eb9cb91@syzkaller.appspotmail.com,
	Zhao Feng <zhaofeng2@cmss.chinamobile.com>,
	stable@vger.kernel.org
Subject: [PATCH] greybus: reject messages with claimed size smaller than header
Date: Mon,  9 Nov 2026 09:33:36 +0800	[thread overview]
Message-ID: <20261109013336.1122-1-zhaofeng2@cmss.chinamobile.com> (raw)

gb_connection_recv() performs two sanity checks on received
messages: the receive buffer must hold at least a full message
header, and it must hold at least the message size claimed in the
header.  Neither check verifies that the claimed message size
covers the header itself.

A message claiming a size smaller than sizeof(struct
gb_operation_msg_hdr) (e.g. 7) passes both checks when 8 or more
bytes were received, and the claimed size is then used as the
message size:

- gb_operation_create_incoming() computes
  request_size = msg_size - sizeof(header), which underflows to
  SIZE_MAX.  The request handler then reads payload from a message
  whose payload size is SIZE_MAX; syzbot reported this as a KASAN
  global-buffer-overflow read in gb_svc_request_handler().
- gb_connection_recv_response() similarly computes
  payload_size = size - sizeof(*header) for accepted short
  responses, which underflows the same way.

Reject such messages up front in gb_connection_recv().  A claimed
size equal to the header size is valid (header only, no payload),
so the comparison must be strict.

Reported-by: syzbot+693652ded53d3eb9cb91@syzkaller.appspotmail.com
Closes: https://syzbot.org/bug?extid=693652ded53d3eb9cb91
Cc: stable@vger.kernel.org
Signed-off-by: Zhao Feng <zhaofeng2@cmss.chinamobile.com>
---
No Fixes tag: the missing validation dates back to the original
greybus import; the introducing commit could not be verified with
the trees available to me.

Not runtime-tested (no greybus hardware).  The affected function is
identical in current upstream master, so the patch applies there
as-is.

This also answers the question raised on the syzbot thread about
whether the underflow is reachable: it is, because the existing
checks compare the *received* size against the claimed size, never
the claimed size against the header size.

 drivers/greybus/operation.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/greybus/operation.c b/drivers/greybus/operation.c
index 8459e9bc07..83b16c78f7 100644
--- a/drivers/greybus/operation.c
+++ b/drivers/greybus/operation.c
@@ -1046,6 +1046,12 @@ void gb_connection_recv(struct gb_connection *connection,
 	/* Use memcpy as data may be unaligned */
 	memcpy(&header, data, sizeof(header));
 	msg_size = le16_to_cpu(header.size);
+	if (msg_size < sizeof(header)) {
+		dev_err_ratelimited(dev,
+				    "%s: malformed message received (%zu < %zu)\n",
+				    connection->name, msg_size, sizeof(header));
+		return;
+	}
 	if (size < msg_size) {
 		dev_err_ratelimited(dev,
 				    "%s: incomplete message 0x%04x of type 0x%02x received (%zu < %zu)\n",
-- 
2.39.2




             reply	other threads:[~2026-11-09  1:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09  1:33 Zhao Feng [this message]
2026-11-09 14:20 ` Alex Elder
2026-11-09 14:21   ` Alex Elder
2026-11-09 14:43 ` Alex Elder

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=20261109013336.1122-1-zhaofeng2@cmss.chinamobile.com \
    --to=zhaofeng2@cmss.chinamobile.com \
    --cc=elder@ieee.org \
    --cc=elder@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+693652ded53d3eb9cb91@syzkaller.appspotmail.com \
    /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®