All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Nirmoy Das" <nirmoyd@nvidia.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: Fix host bridge double put in pci_register_host_bridge()
Date: Mon, 19 Oct 2026 16:24:11 +0000	[thread overview]
Message-ID: <sashiko-outbox-177881@kernel.org> (raw)
In-Reply-To: <20261019161636.2540334-1-nirmoyd@nvidia.com>

> When device_register() fails for the root bus, the unregister path in
> pci_register_host_bridge() drops a bridge reference with put_device()
> and then releases the bus with put_device(&bus->dev). The bus release
> callback, release_pcibus_dev(), also drops bus->bridge, so the bridge
> loses two references for the one taken when the bus was set up.
> 
> This frees the host bridge before pci_register_host_bridge() returns.
> The caller then drops its own reference on freed memory, either in
> pci_create_root_bus() or in the devres action of
> devm_pci_alloc_host_bridge().
> 
> KASAN reports the use after free in pci_host_probe() when the bus device
> registration fails:
> 
>   BUG: KASAN: slab-use-after-free in pci_host_probe+0x17c/0x180
> [ ... ]
> 
> Fixes: 804443c1f278 ("PCI: Fix reference leak in pci_register_host_bridge()")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Nirmoy Das <nirmoyd@nvidia.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261019161636.2540334-1-nirmoyd@nvidia.com?part=1


      reply	other threads:[~2026-10-19 16:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 16:16 [PATCH] PCI: Fix host bridge double put in pci_register_host_bridge() Nirmoy Das
2026-10-19 16:24 ` sashiko-bot [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=sashiko-outbox-177881@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=nirmoyd@nvidia.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.