[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025122430-CVE-2023-54010-9ff1@gregkh>
Date: Wed, 24 Dec 2025 11:56:54 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54010: ACPICA: ACPICA: check null return of ACPI_ALLOCATE_ZEROED in acpi_db_display_objects
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ACPICA: ACPICA: check null return of ACPI_ALLOCATE_ZEROED in acpi_db_display_objects
ACPICA commit 0d5f467d6a0ba852ea3aad68663cbcbd43300fd4
ACPI_ALLOCATE_ZEROED may fails, object_info might be null and will cause
null pointer dereference later.
The Linux kernel CVE team has assigned CVE-2023-54010 to this issue.
Affected and fixed versions
===========================
Fixed in 4.14.316 with commit c9fcb2cfcbd4d7018d9f659f5b670f5b727d1968
Fixed in 4.19.284 with commit 35d67ffad6f5d78dbd800d354f5334c7b71a19e0
Fixed in 5.4.244 with commit c409eb45f5ddae2e3b3faa76cefc87f3cd0d0e88
Fixed in 5.10.181 with commit 978e0d05547ae707d51a942fc7e85a34e181ee6f
Fixed in 5.15.113 with commit d997c920a5305b37f0b8a40501b5aca10d099ecd
Fixed in 6.1.30 with commit fee6133490091492dc66bcf71479bd53bd17a7d2
Fixed in 6.3.4 with commit ed2e1e85644ca3d351324e9927a538c8af4df654
Fixed in 6.4 with commit ae5a0eccc85fc960834dd66e3befc2728284b86c
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-54010
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/acpica/dbnames.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/c9fcb2cfcbd4d7018d9f659f5b670f5b727d1968
https://git.kernel.org/stable/c/35d67ffad6f5d78dbd800d354f5334c7b71a19e0
https://git.kernel.org/stable/c/c409eb45f5ddae2e3b3faa76cefc87f3cd0d0e88
https://git.kernel.org/stable/c/978e0d05547ae707d51a942fc7e85a34e181ee6f
https://git.kernel.org/stable/c/d997c920a5305b37f0b8a40501b5aca10d099ecd
https://git.kernel.org/stable/c/fee6133490091492dc66bcf71479bd53bd17a7d2
https://git.kernel.org/stable/c/ed2e1e85644ca3d351324e9927a538c8af4df654
https://git.kernel.org/stable/c/ae5a0eccc85fc960834dd66e3befc2728284b86c
Powered by blists - more mailing lists