From: Chandradhar Kumar <chandradhar.2003@gmail.com>
To: Alex Elder <elder@ieee.org>
Cc: syzbot <syzbot+693652ded53d3eb9cb91@syzkaller.appspotmail.com>,
elder@kernel.org, gregkh@linuxfoundation.org,
greybus-dev@lists.linaro.org, johan@kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-staging@lists.linux.dev, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [greybus?] [usb?] KASAN: slab-out-of-bounds Read in gb_svc_request_handler
Date: Sat, 7 Nov 2026 19:47:51 +0530 [thread overview]
Message-ID: <au8s1_tIBa0mpTSL@TheRealOne> (raw)
In-Reply-To: <46a139a9-198c-45c1-b41c-521def10a0df@ieee.org>
On Thu, Nov 05, 2026 at 08:08:01AM -0600, Alex Elder wrote:
> Here is what I see happening at the beginning of gb_connection_recv():
> - If the connection is disabled or offloaded, return immediately
> - If the size of the buffer (passed in as the "size" argument) is less
> than the size of an operation message header, return
> - If the 16-bit size embedded in the message header is less than the
> size of the buffer, return
>
> In other words, after these checks, we know:
>
> sizeof(header) <= buffer size (size) AND
> buffer size (size) <= size encoded in the header (msg_size)
No, it does not verify this, it verify:
size encoded in the header <= size (buffer size)
>
> Therefore (transitive property), this is true:
>
> sizeof(header) <= size encoded in the header (msg_size)
So, the transitive property is not true.
I have sent a patch for this bug which verify the msg_size and header
separately, which fixes the out of bounds read.
patch link: https://lore.kernel.org/all/20261106094303.55158-1-chandradhar.2003@gmail.com/
Hey please review the patch if there is something wrong or there are any
other way to fix the bug.
Thanks.
>
> And it's not possible after these checks for this to be true:
>
> header.size < sizeof(struct gb_operation_msg_hdr)
>
> or put another way:
>
> msg_size < sizeof(header) cannot hold
>
>
> It surprises me this would be missed in the AI summary--and I
> fear I'm mistaken. If I'm missing something or wrong about this,
> please feel free to say so.
>
> -Alex
next prev parent reply other threads:[~2026-11-07 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 11:09 [syzbot] [greybus?] [usb?] KASAN: slab-out-of-bounds Read in gb_svc_request_handler syzbot
2026-11-05 14:08 ` Alex Elder
2026-11-07 14:17 ` Chandradhar Kumar [this message]
2026-11-09 14:28 ` 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=au8s1_tIBa0mpTSL@TheRealOne \
--to=chandradhar.2003@gmail.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=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+693652ded53d3eb9cb91@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.