Description
In the Linux kernel, the following vulnerability has been resolved: memblock: make memblock_set_node() also warn about use of MAX_NUMNODES On an (old) x86 system with SRAT just covering space above 4Gb: ACPI: SRAT: Node 0 PXM 0 [mem 0x100000000-0xfffffffff] hotplug the commit referenced below leads to this NUMA configuration no longer being refused by a CONFIG_NUMA=y kernel (previously NUMA: nodes only cover 6144MB of your 8185MB e820 RAM. Not used. No NUMA configuration found Faking a node at [mem 0x0000000000000000-0x000000027fffffff] was seen in the log directly after the message quoted above), because of memblock_validate_numa_coverage() checking for NUMA_NO_NODE (only). This in turn led to memblock_alloc_range_nid()'s warning about MAX_NUMNODES triggering, followed by a NULL deref in memmap_init() when trying to access node 64's (NODE_SHIFT=6) node data. To compensate said change, make memblock_set_node() warn on and adjust a passed in value of MAX_NUMNODES, just like various other functions already do.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
6fdc770506eb8379bf68a49d4e193c8364ac64e0 to < 4ddb7f966f3d06fcf1ba5ee298af6714b593584baffectedff6c3d81f2e86b63a3a530683f89ef393882782a to < 22f742b8f738918f683198a18ec3c691acda14c4affectedff6c3d81f2e86b63a3a530683f89ef393882782a to < e0eec24e2e199873f43df99ec39773ad3af2bff7affected6.6.70 to < 6.6.72affected
Linux Linux
Default version status: affected
6.8affected0 to < 6.8unaffected6.6.72 to ≤ 6.6.*unaffected6.9.6 to ≤ 6.9.*unaffected6.10 to ≤ *unaffected