https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Sun, 31 May 2026 20:56:32 +0000 https://vulnerability.circl.lu/sighting/d88d56f8-dc20-453e-97f0-f5b8bb77f77b/export {"uuid": "d88d56f8-dc20-453e-97f0-f5b8bb77f77b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-40917", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2126", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-40917\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nmemblock: make memblock_set_node() also warn about use of MAX_NUMNODES\n\nOn an (old) x86 system with SRAT just covering space above 4Gb:\n\n ACPI: SRAT: Node 0 PXM 0 [mem 0x100000000-0xfffffffff] hotplug\n\nthe commit referenced below leads to this NUMA configuration no longer\nbeing refused by a CONFIG_NUMA=y kernel (previously\n\n NUMA: nodes only cover 6144MB of your 8185MB e820 RAM. Not used.\n No NUMA configuration found\n Faking a node at [mem 0x0000000000000000-0x000000027fffffff]\n\nwas seen in the log directly after the message quoted above), because of\nmemblock_validate_numa_coverage() checking for NUMA_NO_NODE (only). This\nin turn led to memblock_alloc_range_nid()'s warning about MAX_NUMNODES\ntriggering, followed by a NULL deref in memmap_init() when trying to\naccess node 64's (NODE_SHIFT=6) node data.\n\nTo compensate said change, make memblock_set_node() warn on and adjust\na passed in value of MAX_NUMNODES, just like various other functions\nalready do.\n\ud83d\udccf Published: 2024-07-12T12:25:00.175Z\n\ud83d\udccf Modified: 2025-01-17T13:26:57.833Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/4ddb7f966f3d06fcf1ba5ee298af6714b593584b\n2. https://git.kernel.org/stable/c/22f742b8f738918f683198a18ec3c691acda14c4\n3. https://git.kernel.org/stable/c/e0eec24e2e199873f43df99ec39773ad3af2bff7", "creation_timestamp": "2025-01-17T13:56:48.000000Z"} {"uuid": "d88d56f8-dc20-453e-97f0-f5b8bb77f77b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-40917", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2126", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-40917\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nmemblock: make memblock_set_node() also warn about use of MAX_NUMNODES\n\nOn an (old) x86 system with SRAT just covering space above 4Gb:\n\n ACPI: SRAT: Node 0 PXM 0 [mem 0x100000000-0xfffffffff] hotplug\n\nthe commit referenced below leads to this NUMA configuration no longer\nbeing refused by a CONFIG_NUMA=y kernel (previously\n\n NUMA: nodes only cover 6144MB of your 8185MB e820 RAM. Not used.\n No NUMA configuration found\n Faking a node at [mem 0x0000000000000000-0x000000027fffffff]\n\nwas seen in the log directly after the message quoted above), because of\nmemblock_validate_numa_coverage() checking for NUMA_NO_NODE (only). This\nin turn led to memblock_alloc_range_nid()'s warning about MAX_NUMNODES\ntriggering, followed by a NULL deref in memmap_init() when trying to\naccess node 64's (NODE_SHIFT=6) node data.\n\nTo compensate said change, make memblock_set_node() warn on and adjust\na passed in value of MAX_NUMNODES, just like various other functions\nalready do.\n\ud83d\udccf Published: 2024-07-12T12:25:00.175Z\n\ud83d\udccf Modified: 2025-01-17T13:26:57.833Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/4ddb7f966f3d06fcf1ba5ee298af6714b593584b\n2. https://git.kernel.org/stable/c/22f742b8f738918f683198a18ec3c691acda14c4\n3. https://git.kernel.org/stable/c/e0eec24e2e199873f43df99ec39773ad3af2bff7", "creation_timestamp": "2025-01-17T13:56:48.000000Z"} https://vulnerability.circl.lu/sighting/d88d56f8-dc20-453e-97f0-f5b8bb77f77b/export Fri, 17 Jan 2025 13:56:48 +0000