Answer in brief
CVE-2026-89961 records a High severity (CVSS 7.8) vulnerability in powerpc/mm: fix wrong addr_pfn tracking in compound vmemmap population. 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.
CVSS is 7.8. 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 | >=f2b79c0d79683d552369bb9a7282c1f0226fc566 <b96be860673f9fbbf12cdadb0b25fc4d6d4d207f || >=f2b79c0d79683d552369bb9a7282c1f0226fc566 <e163c7184acf36ac20a248498f4a16016057ca01 || >=f2b79c0d79683d552369bb9a7282c1f0226fc566 <9c914b7a0bd18834505c65f22225ce22c152b2d9 || >=f2b79c0d79683d552369bb9a7282c1f0226fc566 <7968852a7ca3ce81477ec5b4494a28d612f35a97 || >=f2b79c0d79683d552369bb9a7282c1f0226fc566 <89a4ae32764172468dea303eb6ae90fe6c859712 | b96be860673f9fbbf12cdadb0b25fc4d6d4d207f, e163c7184acf36ac20a248498f4a16016057ca01, 9c914b7a0bd18834505c65f22225ce22c152b2d9, 7968852a7ca3ce81477ec5b4494a28d612f35a97, 89a4ae32764172468dea303eb6ae90fe6c859712 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 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/mm: fix wrong addr_pfn tracking in compound vmemmap population vmemmap_populate_compound_pages() uses addr_pfn to determine the PFN offset within a compound page and to decide whether the current vmemmap slot should be populated as a head page mapping or should reuse a tail page mapping. However, addr_pfn is advanced manually in parallel with addr. The loop itself progresses in vmemmap address space, so each PAGE_SIZE step in addr covers PAGE_SIZE / sizeof(struct page) struct page slots. Since addr_pfn is compared against nr_pages in data-PFN units, it should advance by the same number of PFNs. The existing manual increments do not match that and therefore do not reliably track the PFN corresponding to the current addr. As a result, pfn_offset can be computed from the wrong PFN and the code can make the head/tail decision for the wrong compound-page position. Fix this by deriving addr_pfn directly from the current vmemmap address instead of carrying it as loop state.
Quoted source text, attributed separately from HOL analysis.