From: Johan Hovold <johan@kernel.org>
To: Dan Carpenter <error27@gmail.com>
Cc: Alex Elder <elder@ieee.org>, Maritu Hone <marehone12@gmail.com>,
Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bryan O'Donoghue <bod@kernel.org>,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, outreachy@lists.linux.dev
Subject: Re: [PATCH] staging: greybus: uart: fix heap buffer overflow in gb_tty->buffer
Date: Tue, 3 Nov 2026 10:12:50 +0100 [thread overview]
Message-ID: <aumlkgtsSDS1fw4g@hovoldconsulting.com> (raw)
In-Reply-To: <aumfB5MLWIQuTYY3@stanley.mountain>
On Tue, Nov 03, 2026 at 11:44:55AM +0300, Dan Carpenter wrote:
> On Mon, Nov 02, 2026 at 03:33:58PM -0600, Alex Elder wrote:
> > On 11/2/26 1:53 PM, Maritu Hone wrote:
> > > gb_tty->buffer is allocated once in gb_uart_probe() and reused for
> > > every outgoing chunk as the backing store for a
> > > struct gb_uart_send_data_request:
> > >
> > > struct gb_uart_send_data_request {
> > > __le16 size;
> > > __u8 data[];
> > > } __packed;
> > >
> > > In gb_uart_tx_write_work():
> > >
> > > request = gb_tty->buffer;
> > > ...
> > > send_size = gb_tty->buffer_payload_max;
> > > if (send_size > gb_tty->credits)
> > > send_size = gb_tty->credits;
> > > send_size = kfifo_out_peek(&gb_tty->write_fifo,
> > > &request->data[0], send_size);
> Wow.. Heh... I have read both the original message and your
> message and I still have no idea which function contains the
> actual memcpy() overflow. :P
It's the kfifo_out_peek() in gb_uart_tx_write_work() that may write 2
bytes beyond gb_tty->buffer (as its size is currently just
gb_tty->buffer_payload_max).
Johan
next prev parent reply other threads:[~2026-11-03 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 19:53 Maritu Hone
2026-11-02 21:33 ` Alex Elder
2026-11-03 8:44 ` Dan Carpenter
2026-11-03 9:12 ` Johan Hovold [this message]
2026-11-03 9:28 ` Dan Carpenter
2026-11-03 9:49 ` Johan Hovold
2026-11-03 9:58 ` Dan Carpenter
2026-11-03 9:04 ` Johan Hovold
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=aumlkgtsSDS1fw4g@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=bod@kernel.org \
--cc=elder@ieee.org \
--cc=elder@kernel.org \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=marehone12@gmail.com \
--cc=outreachy@lists.linux.dev \
/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®