projects / linux-block.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 0da3e38) | patch
coredump: don't allow ".." in coredump socket path
authorChristian Brauner <brauner@kernel.org>
Thu, 12 Jun 2025 13:25:20 +0000 (15:25 +0200)
committerChristian Brauner <brauner@kernel.org>
Mon, 16 Jun 2025 15:01:22 +0000 (17:01 +0200)
commitedfe3bdbbb52339cd8c2366402f2702c5ebc15c7
tree7685514eb02bb3693364fa138b540a903ad40860tree
parent0da3e3822cfabf062945e449f91ea3ca529eeaa4commit | diff
coredump: don't allow ".." in coredump socket path

There's no point in allowing to walk upwards for the coredump socket.
We already force userspace to give use a sane path, no symlinks, no
magiclinks, and also block "..". Use an absolute path without any
shenanigans.

Link: https://lore.kernel.org/20250612-work-coredump-massage-v1-6-315c0c34ba94@kernel.org
Signed-off-by: Christian Brauner <brauner@kernel.org>
fs/coredump.c diff | blob | blame | history
Linux 6.x block layer and io_uring tree(s)