From: Andreas Kemnade <andreas@kemnade.info>
To: sashiko-bot@kernel.org
Cc: sashiko-reviews@lists.linux.dev, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v4] drm/omap: dsi: avoid sending bta sync all the time in writes
Date: Mon, 29 Jun 2026 18:59:40 +0200 [thread overview]
Message-ID: <20260629185940.283b101d@kemnade.info> (raw)
In-Reply-To: <20260629160448.13D001F000E9@smtp.kernel.org>
On Mon, 29 Jun 2026 16:04:47 +0000
sashiko-bot@kernel.org wrote:
> > - if (r < 0)
> > + if ((!r) && wait_for_completion_timeout(&completion,
> > + msecs_to_jiffies(500)) == 0)
> > + r = -EIO;
> > +
> > + dsi_unregister_isr_vc(dsi, vc, dsi_completion_handler,
> > + &completion, DSI_VC_IRQ_PACKET_SENT);
> > + if (r)
> > return r;
>
> [Severity: High]
> Could this lead to a stack use-after-free if the timeout is reached?
>
> The wait_for_completion_timeout() can return 0 (timeout), after which
> dsi_unregister_isr_vc() unregisters the ISR and the function returns,
> destroying the on-stack completion.
>
> However, dsi_unregister_isr_vc() doesn't appear to synchronize with the IRQ
> handler. If the hardware IRQ fires right after the timeout and the handler
> executes from its lockless copy of the ISR table, could it call
> dsi_completion_handler() with a dangling pointer to the destroyed stack
> frame?
There are several places in this file having that problem. So it is not new.
I have sent a fix here:
https://lore.kernel.org/lkml/20260629-dsi-uaf-v1-1-a5e894f4e4d1@kemnade.info/T/#u
Regards,
Andreas
next prev parent reply other threads:[~2026-06-29 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 15:50 [PATCH v4] drm/omap: dsi: avoid sending bta sync all the time in writes Andreas Kemnade
2026-06-29 16:04 ` sashiko-bot
2026-06-29 16:48 ` Andreas Kemnade
2026-06-29 16:59 ` Andreas Kemnade [this message]
2026-06-30 5:42 ` Ivaylo Dimitrov
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=20260629185940.283b101d@kemnade.info \
--to=andreas@kemnade.info \
--cc=dri-devel@lists.freedesktop.org \
--cc=sashiko-bot@kernel.org \
--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.