linux-kernel - Re: [PATCH v2] gpio: virtuser: fix UAF in configfs release path

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] [day] [month] [year] [list]

Message-ID: <176950538639.14023.10229567374455887978.b4-ty@oss.qualcomm.com>
Date: Tue, 27 Jan 2026 10:17:16 +0100
From: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>
To: linux-gpio@...r.kernel.org, Yuhao Huang <nekowong743@...il.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>, brgl@...ev.pl,
        linux-kernel@...r.kernel.org, Linus Walleij <linusw@...nel.org>
Subject: Re: [PATCH v2] gpio: virtuser: fix UAF in configfs release path


On Mon, 26 Jan 2026 12:03:48 +0800, Yuhao Huang wrote:
> The gpio-virtuser configfs release path uses guard(mutex) to protect
> the device structure. However, the device is freed before the guard
> cleanup runs, causing mutex_unlock() to operate on freed memory.
> 
> Specifically, gpio_virtuser_device_config_group_release() destroys
> the mutex and frees the device while still inside the guard(mutex)
> scope. When the function returns, the guard cleanup invokes
> mutex_unlock(&dev->lock), resulting in a slab use-after-free.
> 
> [...]

Applied, thanks!

[1/1] gpio: virtuser: fix UAF in configfs release path
      commit: 320ae0de18e16ad6ba45f4bbc493a3d141d3b94c

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>