cve/published/2024/CVE-2024-34777.mbox

From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2024-34777: dma-mapping: benchmark: fix node id validation

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

dma-mapping: benchmark: fix node id validation

While validating node ids in map_benchmark_ioctl(), node_possible() may
be provided with invalid argument outside of [0,MAX_NUMNODES-1] range
leading to:

BUG: KASAN: wild-memory-access in map_benchmark_ioctl (kernel/dma/map_benchmark.c:214)
Read of size 8 at addr 1fffffff8ccb6398 by task dma_map_benchma/971
CPU: 7 PID: 971 Comm: dma_map_benchma Not tainted 6.9.0-rc6 #37
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)
Call Trace:
 <TASK>
dump_stack_lvl (lib/dump_stack.c:117)
kasan_report (mm/kasan/report.c:603)
kasan_check_range (mm/kasan/generic.c:189)
variable_test_bit (arch/x86/include/asm/bitops.h:227) [inline]
arch_test_bit (arch/x86/include/asm/bitops.h:239) [inline]
_test_bit at (include/asm-generic/bitops/instrumented-non-atomic.h:142) [inline]
node_state (include/linux/nodemask.h:423) [inline]
map_benchmark_ioctl (kernel/dma/map_benchmark.c:214)
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)

Compare node ids with sane bounds first. NUMA_NO_NODE is considered a
special valid case meaning that benchmarking kthreads won't be bound to a
cpuset of a given node.

Found by Linux Verification Center (linuxtesting.org).

The Linux kernel CVE team has assigned CVE-2024-34777 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.11 with commit 65789daa8087e125927230ccb7e1eab13999b0cf and fixed in 5.15.161 with commit 35d31c8bd4722b107f5a2f5ddddce839de04b936
	Issue introduced in 5.11 with commit 65789daa8087e125927230ccb7e1eab13999b0cf and fixed in 6.1.93 with commit c57874265a3c5206d7aece3793bb2fc9abcd7570
	Issue introduced in 5.11 with commit 65789daa8087e125927230ccb7e1eab13999b0cf and fixed in 6.6.33 with commit 34a816d8735f3924b74be8e5bf766ade1f3bd10b
	Issue introduced in 5.11 with commit 65789daa8087e125927230ccb7e1eab13999b0cf and fixed in 6.9.4 with commit 63e7e05a48a35308aeddd7ecccb68363a5988e87
	Issue introduced in 5.11 with commit 65789daa8087e125927230ccb7e1eab13999b0cf and fixed in 6.10 with commit 1ff05e723f7ca30644b8ec3fb093f16312e408ad

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2024-34777
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	kernel/dma/map_benchmark.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/35d31c8bd4722b107f5a2f5ddddce839de04b936
	https://git.kernel.org/stable/c/c57874265a3c5206d7aece3793bb2fc9abcd7570
	https://git.kernel.org/stable/c/34a816d8735f3924b74be8e5bf766ade1f3bd10b
	https://git.kernel.org/stable/c/63e7e05a48a35308aeddd7ecccb68363a5988e87
	https://git.kernel.org/stable/c/1ff05e723f7ca30644b8ec3fb093f16312e408ad