In the Linux kernel, the following vulnerability has been resolved:
dma-mapping: benchmark: handle NUMA_NO_NODE correctly
cpumask_of_node() can be called for NUMA_NO_NODE inside do_map_benchmark()
resulting in the following sanitizer report:
UBSAN: array-index-out-of-bounds in ./arch/x86/include/asm/topology.h:72:28
index -1 is out of range for type 'cpumask [64][1]'
CPU: 1 PID: 990 Comm: dma_map_benchma Not tainted 6.9.0-rc6 #29
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)
Call Trace:
<TASK>
dump_stack_lvl (lib/dump_stack.c:117)
ubsan_epilogue (lib/ubsan.c:232)
__ubsan_handle_out_of_bounds (lib/ubsan.c:429)
cpumask_of_node (arch/x86/include/asm/topology.h:72) [inline]
do_map_benchmark (kernel/dma/map_benchmark.c:104)
map_benchmark_ioctl (kernel/dma/map_benchmark.c:246)
full_proxy_unlocked_ioctl (fs/debugfs/file.c:333)
__x64_sys_ioctl (fs/ioctl.c:890)
do_syscall_64 (arch/x86/entry/common.c:83)
entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)
Use cpumask_of_node() in place when binding a kernel thread to a cpuset
of a particular node.
Note that the provided node id is checked inside map_benchmark_ioctl().
It's just a NUMA_NO_NODE case which is not handled properly later.
Found by Linux Verification Center (linuxtesting.org).
Security readout for executives and security teams
Plain-English summary
CVE-2024-39277 is a Linux kernel bug in the DMA mapping benchmark path. A local user with privileges can trigger incorrect NUMA node handling, causing an out-of-bounds access. The CVSS score is high, but sources do not show active exploitation.
Executive priority
Patch through normal high-severity kernel maintenance, faster for shared compute, developer workstations, and multi-user Linux systems. No source in the bundle confirms active exploitation, so emergency treatment depends on local exposure and patch availability.
Technical view
The flaw occurs when do_map_benchmark() calls cpumask_of_node() with NUMA_NO_NODE. The CVE record shows UBSAN reporting an array index of -1 in x86 topology code during a debugfs ioctl path. Linux stable commits correct the handling of this NUMA_NO_NODE case.
Likely exposure
Exposure is most relevant to systems running affected Linux kernel versions listed in the CVE data, including 5.11 through fixed stable lines around 5.15.161, 6.1.93, 6.6.33, 6.9.4, and 6.10.
Exploitation context
The CVSS vector is local, low complexity, low privileges, and no user interaction. The source bundle says KEV is false and provides no public exploitation evidence. Treat this as a local kernel risk, not a confirmed internet-exploited issue.
Researcher notes
The bug is CWE-125 and appears tied to NUMA_NO_NODE handling in kernel/dma/map_benchmark.c. The trace reaches map_benchmark_ioctl through debugfs. The CVE data provides stable commit references but does not provide exploit details, operational mitigations, or distribution-specific package names.
Mitigation direction
Update to a vendor kernel containing the relevant Linux stable fixes.
Prioritize affected Linux hosts where local users or workloads are less trusted.
Track distribution advisories for backported fixes matching your kernel branch.
If no package is available, request vendor guidance or backport review.
Validation and detection
Inventory Linux kernel versions across servers, workstations, and images.
Compare deployed kernels against the CVE affected and fixed version data.
Check whether vendor advisories map this CVE to installed packages.
Confirm patched systems report an updated kernel after reboot.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.