From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Frank Li <Frank.li@oss.nxp.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Frank.Li@nxp.com, akhilrajeev@nvidia.com,
mukesh.savaliya@oss.qualcomm.com, rafael@kernel.org,
linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH V5 07/14] i3c: master: Fix potential UAF in i3c_device_match()
Date: Sat, 8 Aug 2026 15:07:52 +0200 [thread overview]
Message-ID: <2026080813075281786283@mail.local> (raw)
In-Reply-To: <anY1dU59JIvV-6BB@lizhi-Precision-Tower-5810>
On 07/08/2026 15:43:49-0400, Frank Li wrote:
> On Fri, Aug 07, 2026 at 05:56:31PM +0300, Adrian Hunter wrote:
> > i3c_device_match() dereferences i3cdev->desc without holding the bus
> > normal-use lock. Since the descriptor pointer can be replaced
> > concurrently, the dereference can race with descriptor replacement and
> > result in a use-after-free.
> >
> > Protect access to i3cdev->desc with the normal-use lock. While the lock
> > is held, the descriptor is guaranteed to remain valid, so the NULL check
> > is also unnecessary and can be removed.
> >
> > This change depends on "i3c: master: Fix recursive locking during device
>
> Remove "This change", just depend on ...
>
> > registration". Prior to that change, taking the normal-use lock in
> > i3c_device_match() could recurse on bus->lock during device
> > registration.
> >
> > This fixes "i3c: master: match I3C device through DT and ACPI".
>
> It should be fixes tag, but this patch still not in linus tree yet, not
> sure how alex handle this.
>
I've added the Fixes tag, this works as long as the tree isn't rebased
before send the PR to Linus.
> Alex:
> Maybe rebase i3c tree,
>
> move "i3c: master: Fix recursive locking during device" before
> "i3c: master: match I3C device through DT and ACPI"
>
> Then squash this into "i3c: master: match I3C device through DT and ACPI"
>
> Or simple ignore "this fixes ..." sentense.
>
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
>
> Frank
>
> >
> > Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
> > ---
> >
> >
> > Changes in V4 and V5:
> >
> > None
> >
> > Changes in V3:
> >
> > New patch
> >
> >
> > drivers/i3c/master.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/i3c/master.c b/drivers/i3c/master.c
> > index ee771ac0b203..83e04a2c202a 100644
> > --- a/drivers/i3c/master.c
> > +++ b/drivers/i3c/master.c
> > @@ -347,8 +347,10 @@ static int i3c_device_match(struct device *dev, const struct device_driver *drv)
> > i3cdev = dev_to_i3cdev(dev);
> > i3cdrv = drv_to_i3cdrv(drv);
> >
> > - if (i3cdev->desc && i3cdev->desc->boardinfo)
> > + i3c_bus_normaluse_lock(i3cdev->bus);
> > + if (i3cdev->desc->boardinfo)
> > static_addr_method = i3cdev->desc->boardinfo->static_addr_method;
> > + i3c_bus_normaluse_unlock(i3cdev->bus);
> >
> > /*
> > * SETAASA-based devices need not always have a matching ID since
> > --
> > 2.53.0
> >
>
> --
> linux-i3c mailing list
> linux-i3c@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-i3c
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2026-08-08 13:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 14:56 [PATCH V5 00/14] i3c: Support IBI-based system wakeup Adrian Hunter
2026-08-07 14:56 ` [PATCH V5 01/14] i3c: master: Fix recursive locking during device registration Adrian Hunter
2026-08-07 15:26 ` sashiko-bot
2026-08-07 14:56 ` [PATCH V5 02/14] i3c: Fix unlocked dereference of dev->desc in i3c_device_get_supported_xfer_mode() Adrian Hunter
2026-08-07 15:13 ` sashiko-bot
2026-08-07 14:56 ` [PATCH V5 03/14] i3c: master: Do not treat master device as a duplicate target Adrian Hunter
2026-08-07 15:07 ` sashiko-bot
2026-08-07 14:56 ` [PATCH V5 04/14] i3c: master: Fix use-after-free of master->this Adrian Hunter
2026-08-07 15:14 ` sashiko-bot
2026-08-07 14:56 ` [PATCH V5 05/14] i3c: Make dev->desc locking assumptions explicit Adrian Hunter
2026-08-07 15:20 ` sashiko-bot
2026-08-07 14:56 ` [PATCH V5 06/14] i3c: master: Fix potential UAF in i3c_device_uevent() Adrian Hunter
2026-08-07 15:21 ` sashiko-bot
2026-08-07 14:56 ` [PATCH V5 07/14] i3c: master: Fix potential UAF in i3c_device_match() Adrian Hunter
2026-08-07 15:37 ` sashiko-bot
2026-08-07 19:43 ` Frank Li
2026-08-08 13:07 ` Alexandre Belloni [this message]
2026-08-07 14:56 ` [PATCH V5 08/14] i3c: master: Support IBI-based wakeup capability Adrian Hunter
2026-08-07 15:16 ` sashiko-bot
2026-08-07 14:56 ` [PATCH V5 09/14] i3c: master: Report wakeup events for IBIs Adrian Hunter
2026-08-07 15:41 ` sashiko-bot
2026-08-07 14:56 ` [PATCH V5 10/14] i3c: master: Add helper to query bus wakeup requirements Adrian Hunter
2026-08-07 15:21 ` sashiko-bot
2026-08-07 14:56 ` [PATCH V5 11/14] i3c: master: Reject IBI requests from non-IBI-capable devices Adrian Hunter
2026-08-07 15:26 ` sashiko-bot
2026-08-07 14:56 ` [PATCH V5 12/14] i3c: mipi-i3c-hci-pci: Propagate I3C wakeup requirements to PCI Adrian Hunter
2026-08-07 15:38 ` sashiko-bot
2026-08-07 14:56 ` [PATCH V5 13/14] i3c: mipi-i3c-hci: Factor out i3c_hci_sysdev() Adrian Hunter
2026-08-07 15:40 ` sashiko-bot
2026-08-07 14:56 ` [PATCH V5 14/14] i3c: mipi-i3c-hci: Advertise IBI wakeup capability Adrian Hunter
2026-08-07 15:30 ` sashiko-bot
2026-08-08 13:09 ` [PATCH V5 00/14] i3c: Support IBI-based system wakeup Alexandre Belloni
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=2026080813075281786283@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=Frank.Li@nxp.com \
--cc=Frank.li@oss.nxp.com \
--cc=adrian.hunter@intel.com \
--cc=akhilrajeev@nvidia.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mukesh.savaliya@oss.qualcomm.com \
--cc=rafael@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