linux-kernel - Re: [PATCH] crypto: hisilicon/qm - fix device leak on QoS updates

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: <aSQubH4nwxgmgK_U@hovoldconsulting.com>
Date: Mon, 24 Nov 2025 11:07:40 +0100
From: Johan Hovold <johan@...nel.org>
To: liulongfang <liulongfang@...wei.com>
Cc: Weili Qian <qianweili@...wei.com>, Zhou Wang <wangzhou1@...ilicon.com>,
	Herbert Xu <herbert@...dor.apana.org.au>,
	"David S . Miller" <davem@...emloft.net>,
	Kai Ye <yekai13@...wei.com>, linux-crypto@...r.kernel.org,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] crypto: hisilicon/qm - fix device leak on QoS updates

On Mon, Nov 24, 2025 at 10:03:03AM +0800, liulongfang wrote:
> On 2025/11/21 19:11, Johan Hovold wrote:
> > Make sure to drop the reference taken when looking up the PCI device on
> > QoS updates.

> This issue has already been fixed by the following patch:
> "[PATCH] crypto: hisilicon/qm - Fix device reference leak in qm_get_qos_value".

Ah, sorry for not noticing. I was still using rc5 as base and apparently
forgot to check linux-next.

Johan