CVE-2025-71118: ACPICA: Avoid walking the Namespace if start_node is NULL
In the Linux kernel, the following vulnerability has been resolved:
ACPICA: Avoid walking the Namespace if startnode is NULL
Although commit 0c9992315e73 ("ACPICA: Avoid walking the ACPI Namespace if it is not there") fixed the situation when both startnode and acpigblrootnode are NULL, the Linux kernel mainline now still crashed on Honor Magicbook 14 Pro [1].
That happens due to the access to the member of parentnode in acpinsgetnextnode(). The NULL pointer dereference will always happen, no matter whether or not the startnode is equal to ACPIROOTOBJECT, so move the check of startnode being NULL out of the if block.
Unfortunately, all the attempts to contact Honor have failed, they refused to provide any technical support for Linux.
The bad DSDT table's dump could be found on GitHub [2].
DMI: HONOR FMB-P/FMB-P-PCB, BIOS 1.13 05/08/2025
[ rjw: Subject adjustment, changelog edits ]
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-71118?
CVE-2025-71118 has been classified with a severity level that suggests it poses a moderate risk to system stability and security.
How do I fix CVE-2025-71118?
To fix CVE-2025-71118, users should update to the latest version of the Linux kernel where the vulnerability has been addressed.
What systems are affected by CVE-2025-71118?
CVE-2025-71118 affects the Linux kernel, specifically any versions that utilize the ACPICA framework improperly.
What impact does CVE-2025-71118 have on my system?
CVE-2025-71118 could lead to system instability if the ACPI Namespace is accessed when it is not available.
When was CVE-2025-71118 disclosed?
CVE-2025-71118 was disclosed following a series of patches aimed at improving the robustness of the Linux kernel's ACPICA handling.