linux-cve-announce - CVE-2023-53636: clk: microchip: fix potential UAF in auxdev release callback

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

Message-ID: <2025100714-CVE-2023-53636-20bd@gregkh>
Date: Tue,  7 Oct 2025 17:19:41 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53636: clk: microchip: fix potential UAF in auxdev release callback

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

clk: microchip: fix potential UAF in auxdev release callback

Similar to commit 1c11289b34ab ("peci: cpu: Fix use-after-free in
adev_release()"), the auxiliary device is not torn down in the correct
order. If auxiliary_device_add() fails, the release callback will be
called twice, resulting in a UAF. Due to timing, the auxdev code in this
driver "took inspiration" from the aforementioned commit, and thus its
bugs too!

Moving auxiliary_device_uninit() to the unregister callback instead
avoids the issue.

The Linux kernel CVE team has assigned CVE-2023-53636 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.1 with commit b56bae2dd6fda6baf3bb74af3812676eebdd52f2 and fixed in 6.1.28 with commit 5b4052aa956e11bcd19e50ca559eb38dcb46201b
	Issue introduced in 6.1 with commit b56bae2dd6fda6baf3bb74af3812676eebdd52f2 and fixed in 6.2.15 with commit d7d6dacf39ed102d7667721ca1700022c9c8b11a
	Issue introduced in 6.1 with commit b56bae2dd6fda6baf3bb74af3812676eebdd52f2 and fixed in 6.3.2 with commit 934406b2d42eaf3fc57f5546cc68ff7ab9680bb3
	Issue introduced in 6.1 with commit b56bae2dd6fda6baf3bb74af3812676eebdd52f2 and fixed in 6.4 with commit 7455b7007b9e93bcc2bc9c1c6c73a228e3152069

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2023-53636
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/clk/microchip/clk-mpfs.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/5b4052aa956e11bcd19e50ca559eb38dcb46201b
	https://git.kernel.org/stable/c/d7d6dacf39ed102d7667721ca1700022c9c8b11a
	https://git.kernel.org/stable/c/934406b2d42eaf3fc57f5546cc68ff7ab9680bb3
	https://git.kernel.org/stable/c/7455b7007b9e93bcc2bc9c1c6c73a228e3152069