linux-kernel - Re: [PATCH] usb: mtu3: fix possible NULL pointer dereference in ep0_rx

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2025102811-helium-caloric-cac5@gregkh>
Date: Tue, 28 Oct 2025 10:07:19 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Pavel Zhigulin <Pavel.Zhigulin@...persky.com>
Cc: Chunfeng Yun <chunfeng.yun@...iatek.com>, linux-usb@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
	lvc-project@...uxtesting.org
Subject: Re: [PATCH] usb: mtu3: fix possible NULL pointer dereference in
 ep0_rx_state()

On Mon, Oct 27, 2025 at 10:31:50PM +0300, Pavel Zhigulin wrote:
> The function 'ep0_rx_state()' accessed 'mreq->request' before verifying
> that mreq was valid. If 'next_ep0_request()' returned NULL, this could
> lead to a NULL pointer dereference. The return value of
> 'next_ep0_request()' is checked in every other code path except
> here. It appears that the intended 'if (mreq)' check was mistakenly
> written as 'if (req)', since the req pointer cannot be NULL when mreq
> is not NULL.
> 
> Initialize 'mreq' and 'req' to NULL by default, and switch 'req'
> NULL-checking to 'mreq' non-NULL check to prevent invalid memory access.
> 
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
> 
> Fixes: df2069acb005 ("usb: Add MediaTek USB3 DRD driver")
> Signed-off-by: Pavel Zhigulin <Pavel.Zhigulin@...persky.com>
> ---
>  drivers/usb/mtu3/mtu3_gadget_ep0.c | 9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/usb/mtu3/mtu3_gadget_ep0.c b/drivers/usb/mtu3/mtu3_gadget_ep0.c
> index e4fd1bb14a55..ee7466ca4d99 100644
> --- a/drivers/usb/mtu3/mtu3_gadget_ep0.c
> +++ b/drivers/usb/mtu3/mtu3_gadget_ep0.c
> @@ -508,8 +508,8 @@ static int handle_standard_request(struct mtu3 *mtu,
>  /* receive an data packet (OUT) */
>  static void ep0_rx_state(struct mtu3 *mtu)
>  {
> -	struct mtu3_request *mreq;
> -	struct usb_request *req;
> +	struct mtu3_request *mreq = NULL;
> +	struct usb_request *req = NULL;
>  	void __iomem *mbase = mtu->mac_base;
>  	u32 maxp;
>  	u32 csr;
> @@ -519,10 +519,11 @@ static void ep0_rx_state(struct mtu3 *mtu)
> 
>  	csr = mtu3_readl(mbase, U3D_EP0CSR) & EP0_W1C_BITS;
>  	mreq = next_ep0_request(mtu);
> -	req = &mreq->request;
> 
>  	/* read packet and ack; or stall because of gadget driver bug */
> -	if (req) {
> +	if (mreq) {
> +		req = &mreq->request;
> +
>  		void *buf = req->buf + req->actual;
>  		unsigned int len = req->length - req->actual;
> 
> --
> 2.43.0
> 
> 

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- You have marked a patch with a "Fixes:" tag for a commit that is in an
  older released kernel, yet you do not have a cc: stable line in the
  signed-off-by area at all, which means that the patch will not be
  applied to any older kernel releases.  To properly fix this, please
  follow the documented rules in the
  Documentation/process/stable-kernel-rules.rst file for how to resolve
  this.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot