ACPICA: Avoid walking the Namespace if start_node is NULL
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: ACPICA: Avoid walking the Namespace if start_node is NULL Although commit 0c9992315e73 ("ACPICA: Avoid walking the ACPI Namespace if it is not there") fixed the situation when both start_node and acpi_gbl_root_node 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 parent_node in acpi_ns_get_next_node(). The NULL pointer dereference will always happen, no matter whether or not the start_node is equal to ACPI_ROOT_OBJECT, so move the check of start_node 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 ]
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in b84edef48cc8afb41150949a87dcfa81bc95b53e; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in ecb296286c8787895625bd4c53e9478db4ae139c; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 7f9b951ed11842373851dd3c91860778356d62d3; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 1bc34293dfbd266c29875206849b4f8e8177e6df; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 0d8bb08126920fd4b12dbf32d9250757c9064b36; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in f91dad0a3b381244183ffbea4cec5a7a69d6f41e; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 9d6c58dae8f6590c746ac5d0012ffe14a77539f0
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 5.10.248; From 5.11.0 · fixed in 5.15.198; From 5.16.0 · fixed in 6.1.160; From 6.2.0 · fixed in 6.6.120; From 6.7.0 · fixed in 6.12.64; From 6.13.0 · fixed in 6.18.3
References 7
git.kernel.org
- stable/c/b84edef48cc8afb41150949a87dcfa81bc95b53e
- stable/c/ecb296286c8787895625bd4c53e9478db4ae139c
- stable/c/7f9b951ed11842373851dd3c91860778356d62d3
- stable/c/1bc34293dfbd266c29875206849b4f8e8177e6df
- stable/c/0d8bb08126920fd4b12dbf32d9250757c9064b36
- stable/c/f91dad0a3b381244183ffbea4cec5a7a69d6f41e
- stable/c/9d6c58dae8f6590c746ac5d0012ffe14a77539f0