summaryrefslogtreecommitdiffstats
path: root/fs/d_path.c
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2021-06-08 10:12:21 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2021-06-08 10:24:09 -0700
commit591a22c14d3f45cc38bd1931c593c221df2f1881 (patch)
treea401c5309eec40ab5304390474e923871e96c509 /fs/d_path.c
parent4c8684fe555e95100030bd330d0a2780ac27952e (diff)
downloadlinux-591a22c14d3f45cc38bd1931c593c221df2f1881.tar.gz
linux-591a22c14d3f45cc38bd1931c593c221df2f1881.tar.bz2
linux-591a22c14d3f45cc38bd1931c593c221df2f1881.zip
proc: Track /proc/$pid/attr/ opener mm_struct
Commit bfb819ea20ce ("proc: Check /proc/$pid/attr/ writes against file opener") tried to make sure that there could not be a confusion between the opener of a /proc/$pid/attr/ file and the writer. It used struct cred to make sure the privileges didn't change. However, there were existing cases where a more privileged thread was passing the opened fd to a differently privileged thread (during container setup). Instead, use mm_struct to track whether the opener and writer are still the same process. (This is what several other proc files already do, though for different reasons.) Reported-by: Christian Brauner <christian.brauner@ubuntu.com> Reported-by: Andrea Righi <andrea.righi@canonical.com> Tested-by: Andrea Righi <andrea.righi@canonical.com> Fixes: bfb819ea20ce ("proc: Check /proc/$pid/attr/ writes against file opener") Cc: stable@vger.kernel.org Signed-off-by: Kees Cook <keescook@chromium.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/d_path.c')
0 files changed, 0 insertions, 0 deletions