DEBIAN-CVE-2024-40917
- Source
- https://security-tracker.debian.org/tracker/CVE-2024-40917
- Import Source
- https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2024-40917.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/DEBIAN-CVE-2024-40917
- Upstream
- Published
- 2024-07-12T13:15:14Z
- Modified
- 2025-10-04T08:01:36Z
- Severity
-
- 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- [none]
- Details
-
In the Linux kernel, the following vulnerability has been resolved: memblock: make memblocksetnode() also warn about use of MAXNUMNODES 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 CONFIGNUMA=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 memblockvalidatenumacoverage() checking for NUMANONODE (only). This in turn led to memblockallocrangenid()'s warning about MAXNUMNODES triggering, followed by a NULL deref in memmapinit() when trying to access node 64's (NODESHIFT=6) node data. To compensate said change, make memblocksetnode() warn on and adjust a passed in value of MAXNUMNODES, just like various other functions already do.
- References
Affected packages
Debian:13 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source
Debian:14 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source