From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Anshika Jain <anshikajain196872@gmail.com>
Cc: Andy Shevchenko <andy@kernel.org>,
sashiko-bot@kernel.org, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: fbtft: fix len<=0 buffer overflow in define_fbtft_write_reg()
Date: Wed, 2 Sep 2026 07:58:44 +0200 [thread overview]
Message-ID: <2026090225-counting-headroom-4efc@gregkh> (raw)
In-Reply-To: <20260902045026.7442-1-anshikajain196872@gmail.com>
On Wed, Sep 02, 2026 at 10:20:26AM +0530, Anshika Jain wrote:
> If len is 0 or negative when a define_fbtft_write_reg()-generated
> function is called, len-- underflows to -1, causing the subsequent
> while (i--) loop to run approximately 2^31 times and write far past
> the end of buf.
>
> This is a latent bug: nothing in the current code prevents two
> adjacent negative values in an init_sequence from producing len=0,
> and there is no guarantee future or out-of-tree panel definitions
> won't do so.
>
> Add an early return for len <= 0, matching the existing guard already
> present in the sibling function fbtft_write_reg8_bus9().
>
> Reported-by: sashiko-bot <sashiko-bot@kernel.org>
> Link: https://sashiko.dev/#/patchset/20260830161529.14500-1-anshikajain196872@gmail.com?part=1
>
> Signed-off-by: Anshika Jain <anshikajain196872@gmail.com>
> ---
> drivers/staging/fbtft/fbtft-bus.c | 3 +++
> 1 file changed, 3 insertions(+)
Did you forget an assisted-by: tag that helped you write this patch and
changelog?
thanks,
greg k-h
next prev parent reply other threads:[~2026-09-02 5:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 4:50 [PATCH] staging: fbtft: fix len<=0 buffer overflow in define_fbtft_write_reg() Anshika Jain
2026-09-02 5:58 ` Greg Kroah-Hartman [this message]
2026-09-02 12:25 ` Nam Cao
2026-09-02 19:03 ` Anshika Jain
2026-09-03 8:24 ` Nam Cao
2026-09-03 8:29 ` Greg Kroah-Hartman
2026-09-03 7:47 ` sashiko-bot
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=2026090225-counting-headroom-4efc@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andy@kernel.org \
--cc=anshikajain196872@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sashiko-bot@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