Subject: CVE-2024-26946: kprobes/x86: Use copy_from_kernel_nofault() to read from unsafe address

From: Greg Kroah-Hartman <[email-masked]>

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

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

kprobes/x86: Use copy_from_kernel_nofault() to read from unsafe address

Read from an unsafe address with copy_from_kernel_nofault() in
arch_adjust_kprobe_addr() because this function is used before checking
the address is in text or not. Syzcaller bot found a bug and reported
the case if user specifies inaccessible data area,
arch_adjust_kprobe_addr() will cause a kernel panic.

[ mingo: Clarified the comment. ]

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

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

	Issue introduced in 5.18 with commit cc66bb914578 and fixed in 6.1.84 with commit 641768431508
	Issue introduced in 5.18 with commit cc66bb914578 and fixed in 6.6.24 with commit f13edd1871d4
	Issue introduced in 5.18 with commit cc66bb914578 and fixed in 6.7.12 with commit 20fdb21eabae
	Issue introduced in 5.18 with commit cc66bb914578 and fixed in 6.8.3 with commit b69f577308f1
	Issue introduced in 5.18 with commit cc66bb914578 and fixed in 6.9 with commit 4e51653d5d87

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-26946
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:
	arch/x86/kernel/kprobes/core.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/6417684315087904fffe8966d27ca74398c57dd6
	https://git.kernel.org/stable/c/f13edd1871d4fb4ab829aff629d47914e251bae3
	https://git.kernel.org/stable/c/20fdb21eabaeb8f78f8f701f56d14ea0836ec861
	https://git.kernel.org/stable/c/b69f577308f1070004cafac106dd1a44099e5483
	https://git.kernel.org/stable/c/4e51653d5d871f40f1bd5cf95cc7f2d8b33d063b