linux-kernel - Re: [PATCH] platform/x86: int3472: Fix double free of GPIO device during unregister

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: <aPsqA8Zbneaeh3ZL@kekkonen.localdomain>
Date: Fri, 24 Oct 2025 10:25:55 +0300
From: Sakari Ailus <sakari.ailus@...ux.intel.com>
To: Qiu Wenbo <qiuwenbo@...me.org>
Cc: Daniel Scally <djrscally@...il.com>, Hans de Goede <hansg@...nel.org>,
	Qiu Wenbo <qiuwenbo@...insec.com.cn>,
	platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org,
	Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
	Andy Shevchenko <andy@...nel.org>
Subject: Re: [PATCH] platform/x86: int3472: Fix double free of GPIO device
 during unregister

Hi Qiu,

Thanks for the patch.

On Fri, Oct 24, 2025 at 01:05:37PM +0800, Qiu Wenbo wrote:
> From: Qiu Wenbo <qiuwenbo@...insec.com.cn>
> 
> regulator_unregister() already frees the associated GPIO device. On
> ThinkPad X9 (Lunar Lake), this causes a double free issue that leads to
> random failures when other drivers (typically Intel THC) attempt to
> allocate interrupts. The root cause is that the reference count of the
> pinctrl_intel_platform module unexpectedly drops to zero when this
> driver defers its probe.
> 
> This behavior can also be reproduced by unloading the module directly.
> 
> Fix the issue by removing the redundant release of the GPIO device
> during regulator unregistration.
> 
> Fixes: 1e5d088a52c2 ("platform/x86: int3472: Stop using devm_gpiod_get()")

Shouldn't this be also cc'd to stable@

Reviewed-by: Sakari Ailus <sakari.ailus@...ux.intel.com>

-- 
Regards,

Sakari Ailus