mm/hugetlb_cma: Fix null nodemask dereference in hugetlb_cma_alloc_frozen_folio
Subsystems (2)
PATCH v7 1/1 mm/hugetlb_cma: Fix null nodemask dereference in hugetlb_cma_alloc_frozen_folio
alloc_buddy_hugetlb_folio_with_mpol() can pass a NULL nodemask to alloc_fresh_hugetlb_folio() as a fallback to allocate from all nodes. If order is gigantic, alloc_fresh_hugetlb_folio() propagates the NULL nodemask down to hugetlb_cma_alloc_frozen_folio() via alloc_gigantic_frozen_folio().
Additionally, hugetlb_cma_alloc_frozen_folio() previously attempted allocation on hugetlb_cma[nid] without verifying if nid is included in the caller's nodemask. Adding a node_isset(nid, *nodemask) check ensures the initial preferred node allocation honors the memory policy / nodemask.
However, hugetlb_cma_alloc_frozen_folio() dereferences the nodemask in node_isset(nid, *nodemask) and for_each_node_mask(node, *nodemask), leading to a null pointer dereference kernel panic when nodemask is NULL.
Fix this by checking if nodemask is NULL in hugetlb_cma_alloc_frozen_folio() and defaulting it to cpuset_current_mems_allowed. Enclose the allocation attempts within the cpuset seqcount retry loop so that if the cpuset changes concurrently during allocation, the attempts are retried using the updated nodemask. This ensures that the initial node check and fallback loop safely honor the task's cpuset without violating cpuset constraints or causing NULL pointer dereferences or unexpected allocation failures.
From a userspace perspective, this bug allows an unprivileged user to crash the kernel (trigger a panic) by requesting a gigantic hugepage allocation with MPOL_PREFERRED_MANY on a system where CMA is only configured on a subset of NUMA nodes.
This can be reproduced by booting a VM with two NUMA nodes, restricting CMA to Node 1 (e.g., hugetlb_cma=1:1G default_hugepagesz=1G hugepagesz=1G hugepages=0), and running a program that allocates a 1GB hugepage area without reserving, restricts allocation to Node 0 using mbind() with MPOL_PREFERRED_MANY, and triggers a page fault:
void *ptr = mmap(NULL, 1UL << 30, PROT_READ | PROT_WRITE,
MAP_PRIVATE | MAP_ANONYMOUS | MAP_HUGETLB | MAP_HUGE_1GB | MAP_NORESERVE, -1, 0);
unsigned long nodemask = 1; /* Node 0 */ mbind(ptr, 1UL << 30, MPOL_PREFERRED_MANY, &nodemask,
sizeof(nodemask) * 8, 0);
memset(ptr, 0, 1UL << 30); /* Trigger fault */
This results in a NULL pointer dereference:
BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP NOPTI RIP: 0010:hugetlb_cma_alloc_frozen_folio+0x75/0x120 Call Trace: <TASK> only_alloc_fresh_hugetlb_folio.isra.0+0x2c/0x160 alloc_surplus_hugetlb_folio+0x6d/0x100 alloc_hugetlb_folio+0x3c5/0x660 hugetlb_no_page+0x3d9/0x650
---
Changes in v7:
- Removed local_node_mask stack variable as suggested by Muchun Song, setting nmask = &cpuset_current_mems_allowed directly to conserve stack space.
- v6: https://lore.kernel.org/linux-mm/[email protected]/
- v5: https://lore.kernel.org/linux-mm/[email protected]/
- v4: https://lore.kernel.org/linux-mm/[email protected]/
- v3: https://lore.kernel.org/linux-mm/[email protected]/
- v2: https://lore.kernel.org/linux-mm/[email protected]/
- v1: https://lore.kernel.org/linux-mm/[email protected]/
mm/hugetlb_cma.c | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-)
mm/hugetlb_cma.c +18 -3
@@ -3,6 +3,7 @@#include <linux/mm.h> #include <linux/cma.h> #include <linux/compiler.h> +#include <linux/cpuset.h> #include <linux/mm_inline.h> #include <asm/page.h>
@@ -30,15 +31,25 @@ struct folio *hugetlb_cma_alloc_frozen_folio(int order, gfp_t gfp_mask,int node;struct folio *folio;struct page *page =NULL ; +const nodemask_t *nmask; +unsigned int cpuset_mems_cookie;if (!hugetlb_cma_size)return NULL ; -if (hugetlb_cma[nid]) +retry_cpuset: +if (!nodemask) { + cpuset_mems_cookie =read_mems_allowed_begin (); + nmask = &cpuset_current_mems_allowed; + }else { + nmask = nodemask; + } + +if (hugetlb_cma[nid] &&node_isset (nid, *nmask)) page =cma_alloc_frozen_compound (hugetlb_cma[nid], order);if (!page && !(gfp_mask & __GFP_THISNODE)) { -for_each_node_mask (node, *nodemask) { +for_each_node_mask (node, *nmask) {if (node == nid || !hugetlb_cma[node])continue ;
@@ -48,8 +59,12 @@ struct folio *hugetlb_cma_alloc_frozen_folio(int order, gfp_t gfp_mask, } } -if (!page) +if (!page) { +if (!nodemask && +unlikely (read_mems_allowed_retry (cpuset_mems_cookie))) + goto retry_cpuset;return NULL ; + } folio =page_folio (page);folio_set_hugetlb_cma (folio);
Signature · 1 line
2.55.0
Quoted 61 lines · Sourav Panda
alloc_buddy_hugetlb_folio_with_mpol()can pass a NULL nodemask toalloc_fresh_hugetlb_folio()as a fallback to allocate from all nodes. If order is gigantic,alloc_fresh_hugetlb_folio()propagates the NULL nodemask down tohugetlb_cma_alloc_frozen_folio()viaalloc_gigantic_frozen_folio().Additionally,
hugetlb_cma_alloc_frozen_folio()previously attempted allocation on hugetlb_cma[nid] without verifying if nid is included in the caller's nodemask. Adding anode_isset(nid, *nodemask)check ensures the initial preferred node allocation honors the memory policy / nodemask.However,
hugetlb_cma_alloc_frozen_folio()dereferences the nodemask innode_isset(nid, *nodemask)andfor_each_node_mask(node, *nodemask), leading to a null pointer dereference kernel panic when nodemask is NULL.Fix this by checking if nodemask is NULL in
hugetlb_cma_alloc_frozen_folio()and defaulting it tocpuset_current_mems_allowed. Enclose the allocation attempts within the cpuset seqcount retry loop so that if the cpuset changes concurrently during allocation, the attempts are retried using the updated nodemask. This ensures that the initial node check and fallback loop safely honor the task's cpuset without violating cpuset constraints or causing NULL pointer dereferences or unexpected allocation failures.From a userspace perspective, this bug allows an unprivileged user to crash the kernel (trigger a panic) by requesting a gigantic hugepage allocation with
MPOL_PREFERRED_MANYon a system where CMA is only configured on a subset of NUMA nodes.This can be reproduced by booting a VM with two NUMA nodes, restricting CMA to Node 1 (e.g., hugetlb_cma=1:1G default_hugepagesz=1G hugepagesz=1G hugepages=0), and running a program that allocates a 1GB hugepage area without reserving, restricts allocation to Node 0 using
mbind()withMPOL_PREFERRED_MANY, and triggers a page fault:void *ptr = mmap(NULL, 1UL << 30,
PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS|MAP_HUGETLB|MAP_HUGE_1GB|MAP_NORESERVE, -1, 0);
unsigned long nodemask = 1; /* Node 0 */ mbind(ptr, 1UL << 30,MPOL_PREFERRED_MANY, &nodemask,sizeof(nodemask) * 8, 0);
memset(ptr, 0, 1UL << 30); /* Trigger fault */This results in a NULL pointer dereference:
BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP NOPTI RIP: 0010:hugetlb_cma_alloc_frozen_folio+0x75/0x120 Call Trace: <TASK> only_alloc_fresh_hugetlb_folio.isra.0+0x2c/0x160 alloc_surplus_hugetlb_folio+0x6d/0x100 alloc_hugetlb_folio+0x3c5/0x660 hugetlb_no_page+0x3d9/0x650
Quoted 3 lines
Fixes eb02f14c4a2b ("mm/hugetlb: allow overcommitting gigantic hugepages")Signed-off-by Sourav Panda <[email protected]>
Thanks.
Quoted 57 lines · Sourav Panda
alloc_buddy_hugetlb_folio_with_mpol()can pass a NULL nodemask toalloc_fresh_hugetlb_folio()as a fallback to allocate from all nodes. If order is gigantic,alloc_fresh_hugetlb_folio()propagates the NULL nodemask down tohugetlb_cma_alloc_frozen_folio()viaalloc_gigantic_frozen_folio().Additionally,
hugetlb_cma_alloc_frozen_folio()previously attempted allocation on hugetlb_cma[nid] without verifying if nid is included in the caller's nodemask. Adding anode_isset(nid, *nodemask)check ensures the initial preferred node allocation honors the memory policy / nodemask.However,
hugetlb_cma_alloc_frozen_folio()dereferences the nodemask innode_isset(nid, *nodemask)andfor_each_node_mask(node, *nodemask), leading to a null pointer dereference kernel panic when nodemask is NULL.Fix this by checking if nodemask is NULL in
hugetlb_cma_alloc_frozen_folio()and defaulting it tocpuset_current_mems_allowed. Enclose the allocation attempts within the cpuset seqcount retry loop so that if the cpuset changes concurrently during allocation, the attempts are retried using the updated nodemask. This ensures that the initial node check and fallback loop safely honor the task's cpuset without violating cpuset constraints or causing NULL pointer dereferences or unexpected allocation failures.From a userspace perspective, this bug allows an unprivileged user to crash the kernel (trigger a panic) by requesting a gigantic hugepage allocation with
MPOL_PREFERRED_MANYon a system where CMA is only configured on a subset of NUMA nodes.This can be reproduced by booting a VM with two NUMA nodes, restricting CMA to Node 1 (e.g., hugetlb_cma=1:1G default_hugepagesz=1G hugepagesz=1G hugepages=0), and running a program that allocates a 1GB hugepage area without reserving, restricts allocation to Node 0 using
mbind()withMPOL_PREFERRED_MANY, and triggers a page fault:void *ptr = mmap(NULL, 1UL << 30,
PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS|MAP_HUGETLB|MAP_HUGE_1GB|MAP_NORESERVE, -1, 0);
unsigned long nodemask = 1; /* Node 0 */ mbind(ptr, 1UL << 30,MPOL_PREFERRED_MANY, &nodemask,sizeof(nodemask) * 8, 0);
memset(ptr, 0, 1UL << 30); /* Trigger fault */This results in a NULL pointer dereference:
BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP NOPTI RIP: 0010:hugetlb_cma_alloc_frozen_folio+0x75/0x120 Call Trace: <TASK> only_alloc_fresh_hugetlb_folio.isra.0+0x2c/0x160 alloc_surplus_hugetlb_folio+0x6d/0x100 alloc_hugetlb_folio+0x3c5/0x660 hugetlb_no_page+0x3d9/0x650
Quoted 3 lines
Fixes eb02f14c4a2b ("mm/hugetlb: allow overcommitting gigantic hugepages")Signed-off-by Sourav Panda <[email protected]>
Quoted 71 lines
---
Changes in v7:
- Removedlocal_node_maskstack variable as suggested by Muchun Song, setting nmask =&cpuset_current_mems_alloweddirectly to conserve stack space.
- v6: https://lore.kernel.org/linux-mm/[email protected]/
- v5: https://lore.kernel.org/linux-mm/[email protected]/
- v4: https://lore.kernel.org/linux-mm/[email protected]/
- v3: https://lore.kernel.org/linux-mm/[email protected]/
- v2: https://lore.kernel.org/linux-mm/[email protected]/
- v1: https://lore.kernel.org/linux-mm/[email protected]/mm/hugetlb_cma.c | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-)mm/hugetlb_cma.c +18
-3@@ -3,6 +3,7 @@#include <linux/mm.h> #include <linux/cma.h> #include <linux/compiler.h> +#include <linux/cpuset.h> #include <linux/mm_inline.h> #include <asm/page.h> @@ -30,15 +31,25 @@ struct folio *hugetlb_cma_alloc_frozen_folio(int order, gfp_t gfp_mask,int node;struct folio *folio;struct page *page =NULL ; +const nodemask_t *nmask; +unsigned int cpuset_mems_cookie;if (!hugetlb_cma_size)return NULL ; -if (hugetlb_cma[nid]) +retry_cpuset: +if (!nodemask) { + cpuset_mems_cookie =read_mems_allowed_begin (); + nmask = &cpuset_current_mems_allowed; + }else { + nmask = nodemask; + } + +if (hugetlb_cma[nid] &&node_isset (nid, *nmask)) page =cma_alloc_frozen_compound (hugetlb_cma[nid], order);if (!page && !(gfp_mask & __GFP_THISNODE)) { -for_each_node_mask (node, *nodemask) { +for_each_node_mask (node, *nmask) {if (node == nid || !hugetlb_cma[node])continue ;@@ -48,8 +59,12 @@ struct folio *hugetlb_cma_alloc_frozen_folio(int order, gfp_t gfp_mask, } } -if (!page) +if (!page) { +if (!nodemask && +unlikely (read_mems_allowed_retry (cpuset_mems_cookie))) + goto retry_cpuset;return NULL ; + } folio =page_folio (page);folio_set_hugetlb_cma (folio);Signature · 1 line
2.55.0
Andrew Morton
maintainerQuoted 24 lines · On Tue, 11 Aug 2026 05:29:09 +0000 Sourav Panda <[email protected]> wrote:
alloc_buddy_hugetlb_folio_with_mpol()can pass a NULL nodemask toalloc_fresh_hugetlb_folio()as a fallback to allocate from all nodes. If order is gigantic,alloc_fresh_hugetlb_folio()propagates the NULL nodemask down tohugetlb_cma_alloc_frozen_folio()viaalloc_gigantic_frozen_folio().Additionally,
hugetlb_cma_alloc_frozen_folio()previously attempted allocation on hugetlb_cma[nid] without verifying if nid is included in the caller's nodemask. Adding anode_isset(nid, *nodemask)check ensures the initial preferred node allocation honors the memory policy / nodemask.However,
hugetlb_cma_alloc_frozen_folio()dereferences the nodemask innode_isset(nid, *nodemask)andfor_each_node_mask(node, *nodemask), leading to a null pointer dereference kernel panic when nodemask is NULL.Fix this by checking if nodemask is NULL in
hugetlb_cma_alloc_frozen_folio()and defaulting it tocpuset_current_mems_allowed. Enclose the allocation attempts within the cpuset seqcount retry loop so that if the cpuset changes concurrently during allocation, the attempts are retried using the updated nodemask. This ensures that the initial node check and fallback loop safely honor the task's cpuset without violating cpuset constraints or causing NULL pointer dereferences or unexpected allocation failures.
Quoted 4 lines
From a userspace perspective, this bug allows an unprivileged user to crash the kernel (trigger a panic) by requesting a gigantic hugepage allocation with
MPOL_PREFERRED_MANYon a system where CMA is only configured on a subset of NUMA nodes.
Thanks. Sashio might have found another thing with MPOL_PREFERRED_MANY and CMA:
https://sashiko.dev/#/patchset/[email protected]
We're days away from 7.2 and I do dislike sending hotfixes upstream at such a late stage. I expect I'll upstream this and a few other hotfixes after 7.2 is released. It'll all end up in the same place.
I would still upstream hotfixes which address added-in-this-cycle bugs, but there aren't any of those at present.
Muchun Song
maintainerQuoted 35 lines · Andrew Morton
Quoted 24 lines · On Tue, 11 Aug 2026 05:29:09 +0000 Sourav Panda <[email protected]> wrote:
alloc_buddy_hugetlb_folio_with_mpol()can pass a NULL nodemask toalloc_fresh_hugetlb_folio()as a fallback to allocate from all nodes. If order is gigantic,alloc_fresh_hugetlb_folio()propagates the NULL nodemask down tohugetlb_cma_alloc_frozen_folio()viaalloc_gigantic_frozen_folio().Additionally,
hugetlb_cma_alloc_frozen_folio()previously attempted allocation on hugetlb_cma[nid] without verifying if nid is included in the caller's nodemask. Adding anode_isset(nid, *nodemask)check ensures the initial preferred node allocation honors the memory policy / nodemask.However,
hugetlb_cma_alloc_frozen_folio()dereferences the nodemask innode_isset(nid, *nodemask)andfor_each_node_mask(node, *nodemask), leading to a null pointer dereference kernel panic when nodemask is NULL.Fix this by checking if nodemask is NULL in
hugetlb_cma_alloc_frozen_folio()and defaulting it tocpuset_current_mems_allowed. Enclose the allocation attempts within the cpuset seqcount retry loop so that if the cpuset changes concurrently during allocation, the attempts are retried using the updated nodemask. This ensures that the initial node check and fallback loop safely honor the task's cpuset without violating cpuset constraints or causing NULL pointer dereferences or unexpected allocation failures.Quoted 4 lines
From a userspace perspective, this bug allows an unprivileged user to crash the kernel (trigger a panic) by requesting a gigantic hugepage allocation with
MPOL_PREFERRED_MANYon a system where CMA is only configured on a subset of NUMA nodes.
Quoted 4 lines
Thanks. Sashio might have found another thing with
MPOL_PREFERRED_MANYand CMA:
Yes, we already noticed that issue in the previous version. However, I believe this should be addressed as a separate patch within alloc_contig_frozen_pages itself, rather than in the HugeTLB code, since this is a low-level memory allocation interface that should not be tied solely to HugeTLB usage.
Muchun,
Thanks.
Quoted 9 lines
We're days away from 7.2 and I do dislike sending hotfixes upstream at such a late stage. I expect I'll upstream this and a few other hotfixes after 7.2 is released. It'll all end up in the same place.
I would still upstream hotfixes which address added-in-this-cycle bugs, but there aren't any of those at present.