[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025102212-CVE-2023-53708-0bf0@gregkh>
Date: Wed, 22 Oct 2025 15:24:47 +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-53708: ACPI: x86: s2idle: Catch multiple ACPI_TYPE_PACKAGE objects
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ACPI: x86: s2idle: Catch multiple ACPI_TYPE_PACKAGE objects
If a badly constructed firmware includes multiple `ACPI_TYPE_PACKAGE`
objects while evaluating the AMD LPS0 _DSM, there will be a memory
leak. Explicitly guard against this.
The Linux kernel CVE team has assigned CVE-2023-53708 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.133 with commit 7b7964cd9db30bc84808a40d13a0633b4313f149
Fixed in 6.1.55 with commit 1ea7e47807279369c82718efd2677ea25c6579e3
Fixed in 6.5.5 with commit 9e8bbde9293151430884aed882a88eaa22298f72
Fixed in 6.6 with commit 883cf0d4cf288313b71146ddebdf5d647b76c78b
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-53708
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/acpi/x86/s2idle.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/7b7964cd9db30bc84808a40d13a0633b4313f149
https://git.kernel.org/stable/c/1ea7e47807279369c82718efd2677ea25c6579e3
https://git.kernel.org/stable/c/9e8bbde9293151430884aed882a88eaa22298f72
https://git.kernel.org/stable/c/883cf0d4cf288313b71146ddebdf5d647b76c78b
Powered by blists - more mailing lists