CVE-2025-71118ACPICA: Avoid walking the Namespace if start_node is NULL
- 5.5MediumCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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
ID reserved
By Linux
- 1 day later
· 1 day later
Published
- 9 months later
· 9 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b84edef48cc8afb41150949a87dcfa81bc95b53e
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ecb296286c8787895625bd4c53e9478db4ae139c
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7f9b951ed11842373851dd3c91860778356d62d3
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1bc34293dfbd266c29875206849b4f8e8177e6df
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 0d8bb08126920fd4b12dbf32d9250757c9064b36
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f91dad0a3b381244183ffbea4cec5a7a69d6f41e
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 9d6c58dae8f6590c746ac5d0012ffe14a77539f0
- affected 2.6.12
- unaffected < 2.6.12
- unaffected 5.10.248 – ≤ 5.10.*
- unaffected 5.15.198 – ≤ 5.15.*
- unaffected 6.1.160 – ≤ 6.1.*
- unaffected 6.6.120 – ≤ 6.6.*
- unaffected 6.12.64 – ≤ 6.12.*
- unaffected 6.18.3 – ≤ 6.18.*
- unaffected 6.19 – ≤ *
References
References7
- https://git.kernel.org/stable/c/b84edef48cc8afb41150949a87dcfa81bc95b53e (opens in a new tab)
- https://git.kernel.org/stable/c/ecb296286c8787895625bd4c53e9478db4ae139c (opens in a new tab)
- https://git.kernel.org/stable/c/7f9b951ed11842373851dd3c91860778356d62d3 (opens in a new tab)
- https://git.kernel.org/stable/c/1bc34293dfbd266c29875206849b4f8e8177e6df (opens in a new tab)
- https://git.kernel.org/stable/c/0d8bb08126920fd4b12dbf32d9250757c9064b36 (opens in a new tab)
- https://git.kernel.org/stable/c/f91dad0a3b381244183ffbea4cec5a7a69d6f41e (opens in a new tab)
- https://git.kernel.org/stable/c/9d6c58dae8f6590c746ac5d0012ffe14a77539f0 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-2493 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-71118)Record last updated .