From: sashiko-bot@kernel.org
To: "Lianjie Wang" <lian@is.s.u-tokyo.ac.jp>
Cc: virtualization@lists.linux.dev,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH 1/2] gpio: virtio: bound the line names block by its configured size
Date: Wed, 04 Nov 2026 20:03:51 +0000 [thread overview]
Message-ID: <sashiko-outbox-197990@kernel.org> (raw)
In-Reply-To: <20261104195632.1702765-1-lian@is.s.u-tokyo.ac.jp>
> virtio_gpio_get_names() walks the line names that the device returns in
> a block of gpio_names_size bytes, which the driver ends with a NUL, and
> checks each name only after stepping past it. If the block holds fewer
> than ngpio names, the walk reaches the end of the block after the last
> name, and the next iteration starts strlen() at the byte after the
> allocation. With a block that holds one name for four lines, KASAN
> reports:
>
> BUG: KASAN: slab-out-of-bounds in strlen+0x57/0x70
> Read of size 1 at addr ffff8880026687c0 by task swapper/0/1
> Call Trace:
> strlen+0x57/0x70
> virtio_gpio_probe+0xcb4/0xfc0
> virtio_dev_probe+0xa7a/0xc50
> Allocated by task 1:
> devm_kmalloc+0x6e/0x280
> virtio_gpio_probe+0xc06/0xfc0
> The buggy address is located 0 bytes to the right of
> allocated 64-byte region [ffff888002668780, ffff8880026687c0)
>
> Check that a name starts inside the block before reading it.
>
> This patch is assisted by Claude Opus 5.5.
>
> Fixes: 3a29355a22c0 ("gpio: Add virtio-gpio driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Lianjie Wang <lian@is.s.u-tokyo.ac.jp>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261104195632.1702765-1-lian@is.s.u-tokyo.ac.jp?part=1
prev parent reply other threads:[~2026-11-04 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 19:56 [PATCH 1/2] gpio: virtio: bound the line names block by its configured size Lianjie Wang
2026-11-04 19:56 ` [PATCH 2/2] gpio: virtio: compute the line names size in a size_t Lianjie Wang
2026-11-04 20:01 ` sashiko-bot
2026-11-04 20:03 ` sashiko-bot [this message]
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=sashiko-outbox-197990@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eperezma@redhat.com \
--cc=lian@is.s.u-tokyo.ac.jp \
--cc=mst@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=virtualization@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