Answer in brief
CVE-2026-89963 records a Unknown severity vulnerability in powerpc/kexec_file: Fix null-ptr-def in extra size calculation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0d3ff067331ef84e7e7f49537d768881042ed5ba <11ef1c2a5dbe0bd8c1345f59bab7331d352f02cf || >=0d3ff067331ef84e7e7f49537d768881042ed5ba <df45337587db21c502fe5251d3bcc7887428f4fb || >=0d3ff067331ef84e7e7f49537d768881042ed5ba <4ff3d9fd71c7bc2fc81afdac1970d9c55a5c0dea || >=0d3ff067331ef84e7e7f49537d768881042ed5ba <761eda315a6e1fda3e8e2185b28430771fb1ac29 | 11ef1c2a5dbe0bd8c1345f59bab7331d352f02cf, df45337587db21c502fe5251d3bcc7887428f4fb, 4ff3d9fd71c7bc2fc81afdac1970d9c55a5c0dea, 761eda315a6e1fda3e8e2185b28430771fb1ac29 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
In the Linux kernel, the following vulnerability has been resolved: powerpc/kexec_file: Fix null-ptr-def in extra size calculation A static Sashiko AI review identified a potential NULL pointer dereference in kexec_extra_fdt_size_ppc64(). On platforms without any reserved memory regions, get_reserved_memory_ranges() can return 0 while leaving 'rmem' unallocated as NULL. Passing it directly leads to a kernel panic when evaluating 'rmem->nr_ranges'. Add a NULL check for 'rmem' to prevent this crash.
Quoted source text, attributed separately from HOL analysis.