CVE-2023-54010
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
In the Linux kernel, a null pointer dereference in ACPICA's acpi_db_display_objects could occur if ACPI_ALLOCATE_ZEROED fails.
Vulnerability in the
Linux kernel's ACPICA subsystem, specifically in the acpi_db_display_objects function. The root cause is that the return value of ACPI_ALLOCATE_ZEROED is not checked for NULL before use. If the memory allocation fails, object_info will be NULL, leading to a null pointer dereference when the code later attempts to access members of that structure [1][2][3].
Exploitation
To trigger this vulnerability, an attacker would need to cause a memory allocation failure within the kernel, which could be achieved by exhausting system memory or through other means that force ACPI_ALLOCATE_ZEROED to return NULL. The attack surface is local, as the function is part of the ACPI debugger interface, which typically requires root privileges to access. However, if an unprivileged user can somehow invoke this code path, they might be able to trigger the null dereference.
Impact
A successful exploitation results in a kernel NULL pointer dereference, which typically causes a system crash (kernel panic) or denial of service disruption. This is a denial-of-service (DoS) vulnerability. There is no evidence from the provided sources that this can lead to privilege escalation or arbitrary code execution.
Mitigation
The vulnerability has been patched in the Linux kernel stable releases. The fix involves adding a NULL check after the allocation and returning an appropriate error code if the allocation fails. Users should update their kernel to a version that includes the commit that addresses this issue [1][2][3].
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
8c9fcb2cfcbd435d67ffad6f5c409eb45f5dd978e0d05547ad997c920a530fee613349009ed2e1e85644cae5a0eccc85fVulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
8- git.kernel.org/stable/c/35d67ffad6f5d78dbd800d354f5334c7b71a19e0nvd
- git.kernel.org/stable/c/978e0d05547ae707d51a942fc7e85a34e181ee6fnvd
- git.kernel.org/stable/c/ae5a0eccc85fc960834dd66e3befc2728284b86cnvd
- git.kernel.org/stable/c/c409eb45f5ddae2e3b3faa76cefc87f3cd0d0e88nvd
- git.kernel.org/stable/c/c9fcb2cfcbd4d7018d9f659f5b670f5b727d1968nvd
- git.kernel.org/stable/c/d997c920a5305b37f0b8a40501b5aca10d099ecdnvd
- git.kernel.org/stable/c/ed2e1e85644ca3d351324e9927a538c8af4df654nvd
- git.kernel.org/stable/c/fee6133490091492dc66bcf71479bd53bd17a7d2nvd
News mentions
0No linked articles in our index yet.