[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025100445-CVE-2023-53544-f48f@gregkh>
Date: Sat, 4 Oct 2025 17:16:58 +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-53544: cpufreq: davinci: Fix clk use after free
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
cpufreq: davinci: Fix clk use after free
The remove function first frees the clks and only then calls
cpufreq_unregister_driver(). If one of the cpufreq callbacks is called
just before cpufreq_unregister_driver() is run, the freed clks might be
used.
The Linux kernel CVE team has assigned CVE-2023-53544 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.33 with commit 6601b8030de3e9c29930684eeac15302a59f991a and fixed in 4.14.308 with commit 66b3bbe6fbd8dd410868e5b53ac3944a934b9310
Issue introduced in 2.6.33 with commit 6601b8030de3e9c29930684eeac15302a59f991a and fixed in 6.1.16 with commit a5f024d0e6f91e05c816ad4ee8837173369dd5cb
Issue introduced in 2.6.33 with commit 6601b8030de3e9c29930684eeac15302a59f991a and fixed in 6.2.3 with commit ab05ae4ab831f64bbc427592c86f599ed9c4324f
Issue introduced in 2.6.33 with commit 6601b8030de3e9c29930684eeac15302a59f991a and fixed in 6.3 with commit 5d8f384a9b4fc50f6a18405f1c08e5a87a77b5b3
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-53544
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/cpufreq/davinci-cpufreq.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/66b3bbe6fbd8dd410868e5b53ac3944a934b9310
https://git.kernel.org/stable/c/a5f024d0e6f91e05c816ad4ee8837173369dd5cb
https://git.kernel.org/stable/c/ab05ae4ab831f64bbc427592c86f599ed9c4324f
https://git.kernel.org/stable/c/5d8f384a9b4fc50f6a18405f1c08e5a87a77b5b3
Powered by blists - more mailing lists