Aleksa Sarai 316a4a329a procfs: block chmod on /proc/thread-self/comm ... commit ccf61486fe upstream. Due to an oversight in commit 1b3044e39a ("procfs: fix pthread cross-thread naming if !PR_DUMPABLE") in switching from REG to NOD, chmod operations on /proc/thread-self/comm were no longer blocked as they are on almost all other procfs files. A very similar situation with /proc/self/environ was used to as a root exploit a long time ago, but procfs has SB_I_NOEXEC so this is simply a correctness issue. Ref: https://lwn.net/Articles/191954/ Ref: 6d76fa58b0 ("Don't allow chmod() on the /proc/<pid>/ files") Fixes: 1b3044e39a ("procfs: fix pthread cross-thread naming if !PR_DUMPABLE") Cc: stable@vger.kernel.org # v4.7+ Signed-off-by: Aleksa Sarai <cyphar@cyphar.com> Message-Id: <20230713141001.27046-1-cyphar@cyphar.com> Signed-off-by: Christian Brauner <brauner@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2023-09-13 09:43:02 +02:00
..
Kconfig	…
Makefile	…
array.c	…
base.c	procfs: block chmod on /proc/thread-self/comm	2023-09-13 09:43:02 +02:00
bootconfig.c	…
cmdline.c	…
consoles.c	…
cpuinfo.c	…
devices.c	…
fd.c	…
fd.h	…
generic.c	…
inode.c	…
internal.h	…
interrupts.c	…
kcore.c	…
kmsg.c	…
loadavg.c	…
meminfo.c	…
namespaces.c	…
nommu.c	…
page.c	…
proc_net.c	…
proc_sysctl.c	sysctl: clarify register_sysctl_init() base directory order	2023-05-17 11:53:46 +02:00
proc_tty.c	…
root.c	…
self.c	…
softirqs.c	…
stat.c	…
task_mmu.c	…
task_nommu.c	…
thread_self.c	…
uptime.c	…
util.c	…
version.c	…
vmcore.c	proc/vmcore: fix signedness bug in read_from_oldmem()	2023-08-03 10:24:14 +02:00