mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pei Xiao <xiaopei01@kylinos.cn>
To: Logan Gunthorpe <logang@deltatee.com>,
	kurt.schwemmer@microsemi.com, bhelgaas@google.com,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2] PCI: switchtec: Fix use-after-free in switchtec_pci_remove due to race condition
Date: Mon, 17 Aug 2026 13:43:58 +0800	[thread overview]
Message-ID: <d6674b24-1a9e-487d-9add-416ee00e6e0d@kylinos.cn> (raw)
In-Reply-To: <5ce42824-488e-4040-8531-0acc8b01b13a@deltatee.com>



在 2026/8/6 23:32, Logan Gunthorpe 写道:
> 
> 
> On 2026-08-05 8:12 p.m., Pei Xiao wrote:
>> In stdev_create, &stdev->mrpc_work is bound with mrpc_event_work, and
>> &stdev->link_event_work is bound with link_event_work. The IRQ handlers
>> switchtec_event_isr and switchtec_dma_mrpc_isr can schedule these works
>> on system_wq (via schedule_work() in the ISRs and via
>> check_link_state_events()).
>>
>> If we remove the device, switchtec_pci_remove makes cleanup and the
>> memory allocated for stdev is released by put_device() ->
>> stdev_release() -> kfree(stdev), while the works mentioned above may
>> still be pending or running. The sequence of operations that may lead
>> to a UAF bug is as follows:
>>
>> CPU0                                      CPU1
>>
>>                                           | switchtec_event_isr
>>                                           | schedule_work(&stdev->mrpc_work)
>> switchtec_pci_remove                      |
>> cdev_device_del(&stdev->cdev,             |
>>                 &stdev->dev)              |
>> stdev_kill(stdev)                         |
>> switchtec_exit_pci(stdev)                 |
>> pci_dev_put(stdev->pdev)                  |
>> put_device(&stdev->dev)                   |
>> // stdev_release -> kfree(stdev)          |
>>                                           | mrpc_event_work
>>                                           | // use stdev (use-after-free)
>>
>> Fix it by quiescing the interrupt sources before canceling the works:
>> stdev_kill() first clears PCI bus mastering, then explicitly frees both
>> IRQs, so no handler can be running and scheduling new work while the works
>> are canceled.
>>
>> Fixes: 080b47def5e5 ("MicroSemi Switchtec management interface driver")
>> Fixes: 48c302dc8f3a ("NTB: switchtec: Add link event notifier callback")
>> Cc: stable@vger.kernel.org
>> Assisted-by: Codex:deepseek-v4-flash
>> Signed-off-by: Pei Xiao <xiaopei01@kylinos.cn>
>> ---
>> changes in v2:
>> 1.Add explicitly devm_free_irq
>> 2.cacel mrpc_work and link_event_work move to before mrpc_timeout
>> 3.Add event_irq and dma_mrpc_irq in struct stdev
>> 4.Add Cc: stable@vger.kernel.org
>> ---
>>  drivers/pci/switch/switchtec.c | 16 +++++++++++++++-
>>  include/linux/switchtec.h      |  2 ++
>>  2 files changed, 17 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/pci/switch/switchtec.c b/drivers/pci/switch/switchtec.c
>> index 5711aaa5df11..235ca1877b6c 100644
>> --- a/drivers/pci/switch/switchtec.c
>> +++ b/drivers/pci/switch/switchtec.c
>> @@ -1318,6 +1318,13 @@ static void stdev_kill(struct switchtec_dev *stdev)
>>  
>>  	pci_clear_master(stdev->pdev);
>>  
>> +	if (stdev->event_irq >= 0)
>> +		devm_free_irq(&stdev->pdev->dev, stdev->event_irq, stdev);
>> +	if (stdev->dma_mrpc_irq >= 0)
>> +		devm_free_irq(&stdev->pdev->dev, stdev->dma_mrpc_irq, stdev);
>> +
>> +	cancel_work_sync(&stdev->mrpc_work);
>> +	cancel_work_sync(&stdev->link_event_work);
>>  	cancel_delayed_work_sync(&stdev->mrpc_timeout);
>>  
>>  	/* Mark the hardware as unavailable and complete all completions */
>> @@ -1356,6 +1363,8 @@ static struct switchtec_dev *stdev_create(struct pci_dev *pdev)
>>  	INIT_LIST_HEAD(&stdev->mrpc_queue);
>>  	mutex_init(&stdev->mrpc_mutex);
>>  	stdev->mrpc_busy = 0;
>> +	stdev->event_irq = -1;
>> +	stdev->dma_mrpc_irq = -1;
> 
> I think the patch as a whole is correct. But one minor nit that could
> maybe clean it up slightly. pci_irq_vector() cannot return 0. So I think
> it would be fine to just leave these explictily initialized to zero and
> check for non-zero in the tests above.
Hi Maintainer,
  I apologize for my delay, and I have already sent the third version.

https://lore.kernel.org/lkml/4cebfe41ee3985bc4f38beb42d44147a34637971.1786944920.git.xiaopei01@kylinos.cn/

Pei.
Thanks.
> 
> Other than that minor point:
> 
> Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
> 
> Thanks!
> 
> Logan


      reply	other threads:[~2026-08-17  5:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06  2:12 Pei Xiao
2026-08-06 15:32 ` Logan Gunthorpe
2026-08-17  5:43   ` Pei Xiao [this message]

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=d6674b24-1a9e-487d-9add-416ee00e6e0d@kylinos.cn \
    --to=xiaopei01@kylinos.cn \
    --cc=bhelgaas@google.com \
    --cc=kurt.schwemmer@microsemi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=logang@deltatee.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

all inboxes | Powered by JetHome®