Subject: CVE-2024-26818: tools/rtla: Fix clang warning about mount_point var size

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

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

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

tools/rtla: Fix clang warning about mount_point var size

clang is reporting this warning:

$ make HOSTCC=clang CC=clang LLVM_IAS=1
[...]
clang -O -g -DVERSION=\"6.8.0-rc3\" -flto=auto -fexceptions
	-fstack-protector-strong -fasynchronous-unwind-tables
	-fstack-clash-protection  -Wall -Werror=format-security
	-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
	$(pkg-config --cflags libtracefs)    -c -o src/utils.o src/utils.c

src/utils.c:548:66: warning: 'fscanf' may overflow; destination buffer in argument 3 has size 1024, but the corresponding specifier may require size 1025 [-Wfortify-source]
  548 |         while (fscanf(fp, "%*s %" STR(MAX_PATH) "s %99s %*s %*d %*d\n", mount_point, type) == 2) {
      |                                                                         ^

Increase mount_point variable size to MAX_PATH+1 to avoid the overflow.

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

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

	Issue introduced in 6.5 with commit a957cbc02531 and fixed in 6.6.18 with commit 8a585914c266
	Issue introduced in 6.5 with commit a957cbc02531 and fixed in 6.7.6 with commit 6bdd43f62ab3
	Issue introduced in 6.5 with commit a957cbc02531 and fixed in 6.8 with commit 30369084ac6e

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-26818
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:
	tools/tracing/rtla/src/utils.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/8a585914c266dc044f53b5c83c170f79b45fcf9a
	https://git.kernel.org/stable/c/6bdd43f62ab3bb5a306af7f0ab857af45777f5a8
	https://git.kernel.org/stable/c/30369084ac6e27479a347899e74f523e6ca29b89