From: Richard Patel <ripatel@wii.dev>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: vkoul@kernel.org, yung-chuan.liao@linux.intel.com,
pierre-louis.bossart@linux.dev, peter.ujfalusi@linux.intel.com,
linux-sound@vger.kernel.org, patches@opensource.cirrus.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] soundwire: intel_auxdevice: Don't disable IRQs before removing children
Date: Thu, 8 Oct 2026 23:11:32 +0000 [thread overview]
Message-ID: <asgjJLeH12OAlYai@wii.dev> (raw)
In-Reply-To: <asePYrXFHxHNssgK@opensource.cirrus.com>
On Thu, Oct 08, 2026 at 01:41:06PM +0100, Charles Keepax wrote:
> On Mon, Oct 05, 2026 at 02:11:47PM +0100, Charles Keepax wrote:
> > On Mon, Oct 05, 2026 at 11:32:05AM +0100, Charles Keepax wrote:
> > > On Sun, Oct 04, 2026 at 12:29:58PM +0000, Richard Patel wrote:
> > > > On Fri, Sep 25, 2026 at 04:42:16PM +0100, Charles Keepax wrote:
> > > > I don't understand the code very well, but isn't there a second UAF
> > > > with the ctx object getting freed? kfree(ctx) in sdw_intel_exit()
> > > > runs well before the IRQ is unregistered.
> > >
> > > This situation is unfortunately fairly complex, the IRQ is shared
> > > between many different functions and only the SoundWire function
> > > relies on ctx. I will do some more poking, but I believe the
> > > free order is such that the soundwire stuff is shutdown before
> > > ctx is freed. I am not 100% certain if that will prevent the
> > > SoundWire IRQ path from getting called, although I would like
> > > to believe it does :-)
> >
> > Hmm... ok so poking this a little more looks like I do see just
> > see these freed in hard the wrong order so we should probably
> > fix that up too. Thanks for spotting that I will have a bit of
> > a think.
>
> Ok found some time to look at this properly I think this is all
> fine. sdw_intel_exit() first calls sdw_intel_cleanup() which will
> eventually call sdw_cdns_enable_interrupt(..., false), which
> should disable the SoundWire IRQs. Then sdw_intel_exit() frees
> the ctx, whilst at that point whilst the IRQ is still registered
> one should no longer be able to see soundwire IRQs, so you shouldn't
> get a dereferencing of ctx.
On my Galaxy Book6, I was able to get a ctx UAF with your v2 patch set
by adding a sleep.
BUG: unable to handle page fault for address: fffffffffffffff8
Oops: Oops: 0000 [#1] SMP NOPTI
CPU: 5 UID: 0 PID: 34491 Comm: irq/165-AudioDS Kdump: loaded Tainted: G OE 7.3.0-rc6-ibt+ #2 PREEMPT(lazy)
RIP: 0010:sdw_intel_thread+0x3c/0x70 [soundwire_intel]
Call Trace:
<TASK>
hda_dsp_interrupt_thread+0x97/0x320 [snd_sof_intel_hda_generic]
irq_thread_fn+0x23/0x60
irq_thread+0xc7/0x190
kthread+0xe5/0x120
</TASK>
--Richard
---
diff --git a/drivers/soundwire/intel_init.c b/drivers/soundwire/intel_init.c
index a7437cd42028..66a08dad7281 100644
--- a/drivers/soundwire/intel_init.c
+++ b/drivers/soundwire/intel_init.c
@@ -155,6 +155,8 @@ irqreturn_t sdw_intel_thread(int irq, void *dev_id)
struct sdw_intel_ctx *ctx = dev_id;
struct sdw_intel_link_res *link;
+ msleep(5000);
+
mutex_lock(&ctx->link_lock);
list_for_each_entry(link, &ctx->link_list, list)
sdw_cdns_irq(irq, link->cdns);
@@ -393,6 +395,7 @@ void sdw_intel_exit(struct sdw_intel_ctx *ctx)
sdw_intel_cleanup(ctx);
kfree(ctx->peripherals);
kfree(ctx->ldev);
+ memset(ctx, 0, sizeof(*ctx));
kfree(ctx);
}
EXPORT_SYMBOL_NS(sdw_intel_exit, "SOUNDWIRE_INTEL_INIT");
next prev parent reply other threads:[~2026-10-08 23:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 15:42 [PATCH v2 0/3] Allow SoundWire devices to communicate during remove Charles Keepax
2026-09-25 15:42 ` [PATCH v2 1/3] soundwire: bus: Don't unassign dev_num before unregistering device Charles Keepax
2026-10-03 8:18 ` Vinod Koul
2026-10-05 9:08 ` Charles Keepax
2026-09-25 15:42 ` [PATCH v2 2/3] soundwire: bus: Expose a helper to remove devices from the bus Charles Keepax
2026-09-25 15:42 ` [PATCH v2 3/3] soundwire: intel_auxdevice: Don't disable IRQs before removing children Charles Keepax
2026-09-26 15:55 ` Pierre-Louis Bossart
2026-09-28 8:39 ` Charles Keepax
2026-09-29 8:34 ` Pierre-Louis Bossart
2026-09-29 12:40 ` Charles Keepax
2026-09-29 18:31 ` Pierre-Louis Bossart
2026-10-04 12:29 ` Richard Patel
2026-10-05 10:32 ` Charles Keepax
2026-10-05 13:11 ` Charles Keepax
2026-10-08 12:41 ` Charles Keepax
2026-10-08 23:11 ` Richard Patel [this message]
2026-09-29 18:34 ` [PATCH v2 0/3] Allow SoundWire devices to communicate during remove Pierre-Louis Bossart
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=asgjJLeH12OAlYai@wii.dev \
--to=ripatel@wii.dev \
--cc=ckeepax@opensource.cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@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