From: sashiko-bot@kernel.org
To: "Zhao Feng" <zhaofeng2@cmss.chinamobile.com>, linux-usb@vger.kernel.org
Subject: Re: [PATCH] USB: serial: mct_u232: fix NULL deref in open error path
Date: Fri, 06 Nov 2026 08:19:12 +0000 [thread overview]
Message-ID: <sashiko-outbox-201050@kernel.org> (raw)
In-Reply-To: <20261106081254.1389-1-zhaofeng2@cmss.chinamobile.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] USB: serial: mct_u232: missing Fixes trailer for commit
35807187e4b3
--
commit aa7ec61a20b2d78c30fb0a49d63ab051c4605906
Author: Zhao Feng <zhaofeng2@cmss.chinamobile.com>
> USB: serial: mct_u232: fix NULL deref in open error path
>
> The MCT U232-P9 has no bulk-in endpoint; received data arrives
> through the interrupt-in endpoint of the second port, whose URB is
> stashed in priv->read_urb by mct_u232_port_probe(). The generic
> port->read_urb is only allocated for ports with a bulk-in endpoint
> and therefore remains NULL for this device.
>
> If submitting the read URB fails in mct_u232_open(), the error
> message dereferences port->read_urb->pipe, causing a NULL pointer
> dereference at offset 0x50 (the pipe field of struct urb), as
> reported by syzbot on KASAN-enabled kernels.
>
> Print the pipe of the URB that was actually submitted instead.
>
> Reported-by: syzbot+58b2d8b19cd6761a395b@syzkaller.appspotmail.com
> Closes: https://syzbot.org/bug?extid=58b2d8b19cd6761a395b
> Cc: stable@vger.kernel.org
> Signed-off-by: Zhao Feng <zhaofeng2@cmss.chinamobile.com>
[Severity: Low]
Prior to 35807187e4b3 ("USB: mct_u232: clean up read implementation"),
mct_u232_startup() assigned rport->interrupt_in_urb to port->read_urb.
That commit moved the URB pointer to priv->read_urb and updated the
usb_submit_urb() call in mct_u232_open(), leaving port->read_urb->pipe in
the error path. Should this include:
Fixes: 35807187e4b3 ("USB: mct_u232: clean up read implementation")
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261106081254.1389-1-zhaofeng2@cmss.chinamobile.com?part=1
next prev parent reply other threads:[~2026-11-06 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 8:12 [PATCH] USB: serial: mct_u232: fix NULL deref in open error path Zhao Feng
2026-11-06 8:19 ` sashiko-bot [this message]
2026-11-06 8:21 ` 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=sashiko-outbox-201050@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=zhaofeng2@cmss.chinamobile.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 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.