From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: 胡连勤 <hulianqin@vivo.com>,
"Mathias Nyman" <mathias.nyman@intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Sarah Sharp" <sarah.a.sharp@linux.intel.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: xhci: check Null pointer in segment alloc
Date: Fri, 19 Dec 2025 14:48:58 +0200 [thread overview]
Message-ID: <4935bdf5-4d36-45c3-9bcd-9d14606dd54e@linux.intel.com> (raw)
In-Reply-To: <TYUPR06MB6217F5AA7DA1E43A567CBA04D2A9A@TYUPR06MB6217.apcprd06.prod.outlook.com>
On 12/19/25 09:18, 胡连勤 wrote:
> From: Lianqin Hu <hulianqin@vivo.com>
>
> Considering that in some extreme cases,
> when a digital headset is connected and a wake-up
> operation is performed,if the headset is plug out
> or the headset connection is abnormally disconnected at this time,
> segment_pool will be set to null, resulting in accessing a null pointer.
>
> So, add null pointer checks to fix the problem.
>
> Call trace:
> dma_pool_alloc+0x3c/0x248
> xhci_segment_alloc+0x9c/0x184
> xhci_alloc_segments_for_ring+0xcc/0x1cc
> xhci_ring_alloc+0xc4/0x1a8
> xhci_endpoint_init+0x36c/0x4ac
> xhci_add_endpoint+0x18c/0x2a4
> usb_hcd_alloc_bandwidth+0x384/0x3e4
> usb_set_interface+0x144/0x510
> usb_reset_and_verify_device+0x248/0x5fc
> usb_port_resume+0x580/0x700
> usb_generic_driver_resume+0x24/0x5c
> usb_resume_both+0x104/0x32c
> usb_runtime_resume+0x18/0x28
> __rpm_callback+0x94/0x3d4
> rpm_resume+0x3f8/0x5fc
> rpm_resume+0x1fc/0x5fc
>
> Fixes: 0ebbab374223 ("USB: xhci: Ring allocation and initialization.")
> Cc: stable@vger.kernel.org
> Signed-off-by: Lianqin Hu <hulianqin@vivo.com>
>
> drivers/usb/host/xhci-mem.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/usb/host/xhci-mem.c b/drivers/usb/host/xhci-mem.c
> index c708bdd69f16..2ea5fb810a80 100644
> --- a/drivers/usb/host/xhci-mem.c
> +++ b/drivers/usb/host/xhci-mem.c
> @@ -35,6 +35,9 @@ static struct xhci_segment *xhci_segment_alloc(struct xhci_hcd *xhci,
> dma_addr_t dma;
> struct device *dev = xhci_to_hcd(xhci)->self.sysdev;
>
> + if (!xhci->segment_pool)
> + return NULL;
> +
The xhci->segment_pool is created in xhci_mem_init() and destroyed in xhci_mem_cleanup().
It should never be NULL when xhci driver tries to allocate a ring segment.
If you can trigger a null pointer dereference here, then please share a backtrace.
There is likely something else is wrong that needs to be fixed.
Thanks
Mathias
next prev parent reply other threads:[~2025-12-19 12:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 7:18 [PATCH] usb: xhci: check Null pointer in segment alloc 胡连勤
2025-12-19 12:48 ` Mathias Nyman [this message]
2025-12-19 15:53 ` 答复: " 胡连勤
2025-12-20 8:08 ` Greg Kroah-Hartman
2025-12-20 11:34 ` 答复: " 胡连勤
2025-12-20 13:15 ` Michal Pecio
2025-12-21 5:48 ` 答复: " 胡连勤
2025-12-22 6:42 ` Lee Jones
2025-12-22 7:13 ` Greg Kroah-Hartman
2025-12-22 7:55 ` Michal Pecio
2025-12-22 12:21 ` 答复: " 胡连勤
2025-12-22 13:34 ` Alan Stern
2025-12-22 16:49 ` Michal Pecio
2025-12-22 17:03 ` Alan Stern
2025-12-22 21:03 ` Michal Pecio
2025-12-23 3:24 ` Alan Stern
2025-12-23 10:06 ` Michal Pecio
2025-12-23 18:37 ` Alan Stern
2025-12-23 19:43 ` Michal Pecio
2025-12-22 14:00 ` 答复: " Greg Kroah-Hartman
2025-12-21 16:22 ` Greg Kroah-Hartman
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=4935bdf5-4d36-45c3-9bcd-9d14606dd54e@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hulianqin@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=sarah.a.sharp@linux.intel.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