CVE-2025-71118: Linux kernel · NULL Pointer Dereference
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f91dad0a3b381244183ffbea4cec5a7a69d6f41e : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-06-10.
- Patch
- Available – fixed in f91dad0a3b381244183ffbea4cec5a7a69d6f41e, ecb296286c8787895625bd4c53e9478db4ae139c, b84edef48cc8afb41150949a87dcfa81bc95b53e +4
Exploitation evidence
Disclosed: evidence found.
CVE published 14 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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 ]
References
- git.kernel.org/stable/c/b84edef48cc8afb41150949a87dcfa81bc95b53e (opens in a new tab)
- git.kernel.org/stable/c/ecb296286c8787895625bd4c53e9478db4ae139c (opens in a new tab)
- git.kernel.org/stable/c/7f9b951ed11842373851dd3c91860778356d62d3 (opens in a new tab)
- git.kernel.org/stable/c/1bc34293dfbd266c29875206849b4f8e8177e6df (opens in a new tab)
- git.kernel.org/stable/c/0d8bb08126920fd4b12dbf32d9250757c9064b36 (opens in a new tab)
- git.kernel.org/stable/c/f91dad0a3b381244183ffbea4cec5a7a69d6f41e (opens in a new tab)
- git.kernel.org/stable/c/9d6c58dae8f6590c746ac5d0012ffe14a77539f0 (opens in a new tab)