From: Michal Pecio <michal.pecio@gmail.com>
To: Mathias Nyman <mathias.nyman@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Guangshuo Li <lgs201920130244@gmail.com>,
Wesley Cheng <quic_wcheng@quicinc.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] usb: xhci: Check kcalloc_node() when allocating interrupter array in xhci_mem_init()
Date: Mon, 3 Nov 2025 12:23:22 +0100 [thread overview]
Message-ID: <20251103122322.5433a7a1.michal.pecio@gmail.com> (raw)
In-Reply-To: <11d7b29d-a45f-48e9-bff5-cb94150d0bdf@intel.com>
On Mon, 3 Nov 2025 13:02:06 +0200, Mathias Nyman wrote:
> > Hi Greg and Mathias,
> >
> > I noticed that this bug still exists in current 6.6 and 6.12 releases,
> > what would be the sensible course of action to fix it?
> >
>
> Not sure this qualifies for stable.
> Is this something that has really happened in real life?
>
> The stable-kernel-rules.rst states it should "fix a real bug that bothers people"
>
> If kcalloc_node() fails to allocate that array of pointers then something
> else is already badly messed up.
I don't know how the reported found it, but it can obviously happen when
the driver is bound to a new xHCI controller under OOM conditions.
So maybe not very often, but xHCI hotplug is a thing in Thunderbolt and
OOM happens sometimes too, so it's not exactly impossible either.
I thought it's usual to fix such bugs when they are known.
Simulated allocation failure before/after:
[ +30,414603] xhci_hcd 0000:00:10.0: xHCI Host Controller
[ +0,000012] xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
[ +0,000159] BUG: kernel NULL pointer dereference, address: 0000000000000000
[ +0,000004] #PF: supervisor read access in kernel mode
[ +0,000002] #PF: error_code(0x0000) - not-present page
[ +0,000002] PGD 0 P4D 0
[ +0,000003] Oops: 0000 [#1] PREEMPT SMP
[ +0,000004] CPU: 1 PID: 4270 Comm: insmod Not tainted 6.6.113 #11
[ +0,000003] Hardware name: HP HP EliteDesk 705 G3 MT/8265, BIOS P06 Ver. 02.45 07/16/2024
[ +0,000003] RIP: 0010:xhci_add_interrupter+0x25/0x130 [xhci_hcd]
[ +0,042495] xhci_hcd 0000:00:10.0: xHCI Host Controller
[ +0,000012] xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
[ +0,007193] xhci_hcd 0000:00:10.0: can't setup: -12
[ +0,000010] xhci_hcd 0000:00:10.0: USB bus 2 deregistered
[ +0,000080] xhci_hcd 0000:00:10.0: init 0000:00:10.0 fail, -12
[ +0,000004] xhci_hcd: probe of 0000:00:10.0 failed with error -12
next prev parent reply other threads:[~2025-11-03 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 13:08 [PATCH] usb: xhci: Check kcalloc_node() when allocating interrupter array in xhci_mem_init() Guangshuo Li
2025-09-18 15:38 ` Michal Pecio
2025-11-03 8:40 ` Michal Pecio
2025-11-03 11:02 ` Mathias Nyman
2025-11-03 11:23 ` Michal Pecio [this message]
2025-11-03 11:49 ` 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=20251103122322.5433a7a1.michal.pecio@gmail.com \
--to=michal.pecio@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=quic_wcheng@quicinc.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox