powerpc/mm: fix wrong addr_pfn tracking in compound vmemmap population
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 7968852a7ca3ce81477ec5b4494a28d612f35a97, Kernel 89a4ae32764172468dea303eb6ae90fe6c859712, Kernel 9c914b7a0bd18834505c65f22225ce22c152b2d9 and 2 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.6, >=f2b79c0d79683d552369bb9a7282c1f0226fc566 <7968852a7ca3ce81477ec5b4494a28d612f35a97, >=f2b79c0d79683d552369bb9a7282c1f0226fc566 <89a4ae32764172468dea303eb6ae90fe6c859712, >=f2b79c0d79683d552369bb9a7282c1f0226fc566 <9c914b7a0bd18834505c65f22225ce22c152b2d9, >=f2b79c0d79683d552369bb9a7282c1f0226fc566 <b96be860673f9fbbf12cdadb0b25fc4d6d4d207f, >=f2b79c0d79683d552369bb9a7282c1f0226fc566 <e163c7184acf36ac20a248498f4a16016057ca01 | 7968852a7ca3ce81477ec5b4494a28d612f35a97, 89a4ae32764172468dea303eb6ae90fe6c859712, 9c914b7a0bd18834505c65f22225ce22c152b2d9, b96be860673f9fbbf12cdadb0b25fc4d6d4d207f, e163c7184acf36ac20a248498f4a16016057ca01 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket