linux-kernel - Re: [PATCH v2 1/3] gpio: mpsse: use rcu to ensure worker is torn down

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aN6NWQukTYWPGu_w@ada.csh.rit.edu>
Date: Thu, 2 Oct 2025 10:34:01 -0400
From: Mary Strodl <mstrodl@....rit.edu>
To: Tzung-Bi Shih <tzungbi@...nel.org>
Cc: Linus Walleij <linus.walleij@...aro.org>, linux-kernel@...r.kernel.org,
	brgl@...ev.pl, linux-gpio@...r.kernel.org,
	"Paul E. McKenney" <paulmck@...nel.org>
Subject: Re: [PATCH v2 1/3] gpio: mpsse: use rcu to ensure worker is torn down

Hello!

On Thu, Oct 02, 2025 at 10:03:33PM +0800, Tzung-Bi Shih wrote:
> To use revocable API, we need to identify what resources should protect.  It
> seems there are some UAF possibilities in gpio_mpsse_poll() after unplugging
> the device.
Yeah, that's what the cancel_work_sync is supposed to protect. This case is a
little weird because the task itself is what could get destroyed on unplug,
but it could be cool to have some guarantees around accessing `priv` and other
resources in the worker?

I'm open to suggestions if you have ideas. Thanks!