From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Haofeng Li <lihaofeng@kylinos.cn>
Cc: Kees Cook <kees@kernel.org>, Melbin K Mathew <mlbnkm1@gmail.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Xu Rao <raoxu@uniontech.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Haofeng Li <13266079573@163.com>
Subject: Re: [PATCH] usb: gadget: f_printer: prevent OOB write in GET_DEVICE_ID
Date: Fri, 21 Aug 2026 13:01:06 +0200 [thread overview]
Message-ID: <2026082154-estrogen-spoon-0a9e@gregkh> (raw)
In-Reply-To: <20260821083428.3234295-1-lihaofeng@kylinos.cn>
On Fri, Aug 21, 2026 at 04:34:28PM +0800, Haofeng Li wrote:
> printer_func_setup() services the Printer Class GET_DEVICE_ID request
> by echoing the PnP string previously stored in the gadget's configfs
> pnp_string attribute:
>
> value = strlen(*dev->pnp_string);
> buf[0] = (value >> 8) & 0xFF;
> buf[1] = value & 0xFF;
> memcpy(buf + 2, *dev->pnp_string, value);
>
> The EP0 response buffer is exactly USB_COMP_EP0_BUFSIZ (4096) bytes,
> allocated once by composite_dev_prepare():
>
> cdev->req->buf = kzalloc(USB_COMP_EP0_BUFSIZ, GFP_KERNEL);
>
> The two-byte length prefix plus the string body must therefore fit
> into 4096 bytes. pnp_string is stored via kstrndup(page, len,
> GFP_KERNEL) in f_printer_opts_pnp_string_store(); configfs passes at
> most PAGE_SIZE - 1 (4095) bytes down to the store callback, so a
> 4095-byte string combined with the 2-byte length field makes the
> memcpy() write buf[2..4096], one byte past the end of the allocation.
>
> Attack chain (USB Printer gadget on the victim device):
>
> 1. pnp_string is set to a 4095-byte value through the gadget's
> configfs attribute
> (~/config/usb_gadget/<gadget>/functions/printer.usb0/pnp_string);
> configfs accepts up to PAGE_SIZE - 1 bytes (fs/configfs/file.c).
> 2. The printer function is enabled and the gadget is bound to its
> UDC. An attacker in control of the connecting USB host sends a
> Printer Class GET_DEVICE_ID request (bmRequestType=0xA1,
> bRequest=0x00, wIndex pointing at the printer interface); the
> usblp host driver also issues this request on enumeration.
> 3. composite_setup() -> printer_func_setup() -> memcpy(buf + 2,
> pnp_string, 4095) performs a 4097-byte write into the 4096-byte
> EP0 response buffer, overflowing the heap object by one byte and
> potentially corrupting adjacent slab objects or allocator
> metadata (CWE-787).
>
> With KASAN enabled the overflow is reliably reported (this is
> reproducible end to end with a configfs gadget + dummy_hcd):
>
> BUG: KASAN: slab-out-of-bounds in printer_func_setup+0x2ec/0x3c0
> Write of size 4095 at addr ffff88818e461002
>
> Fix it at both ends:
>
> - clamp the string length to USB_COMP_EP0_BUFSIZ - 2 in
> printer_func_setup() so the copy can never exceed the EP0 buffer,
> and
> - reject pnp_string values longer than USB_COMP_EP0_BUFSIZ - 2 in
> f_printer_opts_pnp_string_store() so an oversized string is never
> stored in the first place.
>
> Signed-off-by: Haofeng Li <lihaofeng@kylinos.cn>
> ---
> drivers/usb/gadget/function/f_printer.c | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
Did you forget an Assisted-by: tag here?
next prev parent reply other threads:[~2026-08-21 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 8:34 Haofeng Li
2026-08-21 11:01 ` Greg Kroah-Hartman [this message]
2026-08-21 14:41 ` Haofeng Li
2026-08-21 16:05 ` [PATCH v2] " Haofeng Li
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=2026082154-estrogen-spoon-0a9e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=13266079573@163.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kees@kernel.org \
--cc=lihaofeng@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mlbnkm1@gmail.com \
--cc=raoxu@uniontech.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 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®