From: Qasim Ijaz <qasdev00@gmail.com>
To: Johan Hovold <johan@kernel.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2] usb: Fix null-ptr-deref in qt2_process_read_urb()
Date: Mon, 13 Jan 2025 18:12:01 +0000 [thread overview]
Message-ID: <Z4VXcZLcFxA8AQ-b@qasdev.system> (raw)
On Mon, Jan 13, 2025 at 10:00:18AM +0100, Johan Hovold wrote:
> On Sun, Jan 12, 2025 at 09:55:58AM +0000, Qasim Ijaz wrote:
> > This patch addresses a null-ptr-deref in qt2_process_read_urb() due to
> > an incorrect bounds check in the following:
>
> Thanks for the fix. This looks correct, but your patch is whitespace
> damaged (tabs replaced with spaces) and does not apply.
>
> Can you please fix your mail setup and resend a v3? (Make sure to send
> it to yourself first.)
>
> When doing so, please use the common patch prefix for this driver:
>
> USB: serial: quatech2:
>
> > ""
>
> You can drop these (markup?) quotes.
>
> > if (newport > serial->num_ports) {
> > dev_err(&port->dev,
> > "%s - port change to invalid port: %i\n",
> > __func__, newport);
> > break;
> > }
> > ""
> >
> > The condition doesn't account for the valid range of the serial->port
> > buffer, which is from 0 to serial->num_ports - 1. When newport is equal
> > to serial->num_ports, the assignment of "port" in the
> > following code is out-of-bounds and NULL:
> >
> > ""
> > serial_priv->current_port = newport;
> > port = serial->port[serial_priv->current_port];
> >
> > ""
> >
> > The fix checks if newport is greater than or equal to serial->num_ports
> > indicating it is out-of-bounds.
> >
> > Reported-by: syzbot <syzbot+506479ebf12fe435d01a@syzkaller.appspotmail.com>
> > Closes: https://syzkaller.appspot.com/bug?extid=506479ebf12fe435d01a
> > Signed-off-by: Qasim Ijaz <qasdev00@gmail.com>
>
> And please include a Fixes and CC stable tag:
>
> Fixes: f7a33e608d9a ("USB: serial: add quatech2 usb to serial driver")
> Cc: stable@vger.kernel.org # 3.5
>
> Johan
Hi Johan,
Thank you for your feedback on the previous version. I've sent the v3 patch addressing the issues: fixed whitespace damage, removed quotes, updated the prefix, and added Fixes and Cc tags.
Best regards,
Qasim
next reply other threads:[~2025-01-13 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 18:12 Qasim Ijaz [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-12 9:55 [PATCH v2] usb: Fix null-ptr-deref in qt2_process_read_urb() Qasim Ijaz
2025-01-12 13:08 ` Greg Kroah-Hartman
2025-01-13 9:00 ` 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=Z4VXcZLcFxA8AQ-b@qasdev.system \
--to=qasdev00@gmail.com \
--cc=Z4TWIs1fCmVLraBa@hovoldconsulting.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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 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.