From: sashiko-bot@kernel.org
To: "Yingjie Wang" <1075151112@qq.com>, linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: configfs: NUL-terminate extended property data
Date: Thu, 29 Oct 2026 03:16:03 +0000 [thread overview]
Message-ID: <sashiko-outbox-188664@kernel.org> (raw)
In-Reply-To: <tencent_6FF2EBE4EF5FF4F324C8DC4AD0F39588E505@qq.com>
> Unicode extended properties account for a UTF-16 terminator in
> ext_prop->data_len. The configfs store path currently allocates only the
> input bytes, so ext_prop_data_show() copies one byte past the allocation.
>
> Use kmemdup_nul() for the configfs data so the source byte implied by the
> terminator-inclusive length is present for both the configfs readback and
> the descriptor conversion.
>
> Fixes: 7419485f197c ("usb: gadget: configfs: OS Extended Properties descriptors support")
>
> Reported-by: Bingquan Chen <patzilla007@gmail.com>
> Link: https://lore.kernel.org/all/20260421141010.5607-1-patzilla007@gmail.com/
> Cc: stable@vger.kernel.org
>
> Tested: x86-64 KASAN configfs readback through a built-in RNDIS function
> instance. The baseline reports a slab-out-of-bounds read in
> ext_prop_data_show(); the patched kernel reads back the expected 0x41 0x00
> bytes with no KASAN report.
>
> Signed-off-by: Yingjie Wang <1075151112@qq.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/tencent_6FF2EBE4EF5FF4F324C8DC4AD0F39588E505@qq.com?part=1
prev parent reply other threads:[~2026-10-29 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 3:06 [PATCH] usb: gadget: configfs: NUL-terminate extended property data Yingjie Wang
2026-10-29 3:16 ` 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-188664@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=1075151112@qq.com \
--cc=linux-usb@vger.kernel.org \
--cc=sashiko-reviews@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 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.