Linux Test Project
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH STAGING v4 14/16] fchroot11: test failfs entry with no_new_privs
Date: Wed, 14 Oct 2026 16:20:52 +0200	[thread overview]
Message-ID: <as-PxIfrUCyPZjQd@yuki.lan> (raw)
In-Reply-To: <20260831-fchroot-v4-14-57cceb68f927@suse.com>

Hi!
> Verify that an unprivileged process may enter failfs when it
> committed to no_new_privs, since setuid binaries then pose no
> confused deputy risk anymore. The test also verifies that a process
> which entered failfs counts as chrooted: it can no longer create a
> user namespace with unshare() to regain CAP_SYS_CHROOT.
> 
> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> ---
>  runtest/staging                               |  1 +
>  testcases/kernel/syscalls/fchroot/.gitignore  |  1 +
>  testcases/kernel/syscalls/fchroot/fchroot11.c | 70 +++++++++++++++++++++++++++
>  3 files changed, 72 insertions(+)
> 
> diff --git a/runtest/staging b/runtest/staging
> index 9ec2a7897..137e3f99a 100644
> --- a/runtest/staging
> +++ b/runtest/staging
> @@ -10,3 +10,4 @@ fchroot07 fchroot07
>  fchroot08 fchroot08
>  fchroot09 fchroot09
>  fchroot10 fchroot10
> +fchroot11 fchroot11
> diff --git a/testcases/kernel/syscalls/fchroot/.gitignore b/testcases/kernel/syscalls/fchroot/.gitignore
> index 53a1fa1d0..650ef2690 100644
> --- a/testcases/kernel/syscalls/fchroot/.gitignore
> +++ b/testcases/kernel/syscalls/fchroot/.gitignore
> @@ -9,3 +9,4 @@ fchroot07_child
>  fchroot08
>  fchroot09
>  fchroot10
> +fchroot11
> diff --git a/testcases/kernel/syscalls/fchroot/fchroot11.c b/testcases/kernel/syscalls/fchroot/fchroot11.c
> new file mode 100644
> index 000000000..85401e5fe
> --- /dev/null
> +++ b/testcases/kernel/syscalls/fchroot/fchroot11.c
> @@ -0,0 +1,70 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +/*
> + * Copyright (C) 2026 SUSE LLC Andrea Cervesato <andrea.cervesato@suse.com>
> + */
> +
> +/*\
> + * Test unprivileged :manpage:`fchroot(2)` into failfs with no_new_privs
> + * set.
> + *
> + * An unprivileged process may enter failfs when it committed to
> + * no_new_privs, since setuid binaries then pose no confused deputy risk
> + * anymore. The test also verifies that a process which entered failfs
> + * counts as chrooted: it can no longer create a user namespace with
> + * :manpage:`unshare(2)` to regain ``CAP_SYS_CHROOT``.
> + *
> + * The user namespace check requires ``CONFIG_USER_NS``, which is enforced
> + * with ``.needs_kconfigs``.
> + *
> + * Root is required to drop to an unprivileged user in the forked child.
> + */
> +
> +#define _GNU_SOURCE
> +#include <fcntl.h>
> +#include <pwd.h>
> +#include <sched.h>
> +#include "tst_test.h"
> +#include "lapi/fcntl.h"
> +#include "lapi/prctl.h"
> +#include "lapi/sched.h"
> +#include "lapi/syscalls.h"
> +
> +static struct passwd *ltpuser;
> +
> +static void run(void)
> +{
> +	if (SAFE_FORK())
> +		return;
> +
> +	SAFE_SETRESUID(ltpuser->pw_uid, ltpuser->pw_uid,
> +		ltpuser->pw_uid);
> +
> +	SAFE_PRCTL(PR_SET_NO_NEW_PRIVS, 1, 0, 0, 0);
> +
> +	TST_EXP_PASS(tst_syscall(__NR_fchroot, FD_FAILFS_ROOT, 0),
> +		"unprivileged fchroot() with no_new_privs");
> +
> +	TST_EXP_FAIL2(open("/etc/passwd", O_RDONLY), EOPNOTSUPP,
> +		"absolute lookup after entering failfs");

AFAIK there is no /etc/passwd on Android. Maybe we should use /dev/zero
instead?

> +	TST_EXP_FAIL(unshare(CLONE_NEWUSER), EPERM,
> +		"user namespace creation blocked by the failfs root");
> +
> +	exit(0);

Here as well, no need for the exit(0).

> +}
> +
> +static void setup(void)
> +{
> +	ltpuser = SAFE_GETPWNAM("nobody");
> +}
> +
> +static struct tst_test test = {
> +	.setup = setup,
> +	.test_all = run,
> +	.needs_root = 1,
> +	.forks_child = 1,
> +	.needs_kconfigs = (const char *[]) {
> +		"CONFIG_USER_NS=y",
> +		NULL,
> +	}
> +};
> 
> -- 
> 2.51.0
> 
> 
> -- 
> Mailing list info: https://lists.linux.it/listinfo/ltp

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-10-14 14:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  8:00 [LTP] [PATCH v4 00/16] fchroot: add fchroot() testing suite Andrea Cervesato
2026-08-31  8:00 ` [LTP] [PATCH v4 01/16] syscalls: add v7.3 syscall numbers Andrea Cervesato
2026-08-31  8:00 ` [LTP] [PATCH v4 02/16] syscalls: update outdated syscall entries Andrea Cervesato
2026-08-31  8:00 ` [LTP] [PATCH STAGING v4 03/16] lapi: fallback fchroot() parameters Andrea Cervesato
2026-08-31  8:00 ` [LTP] [PATCH STAGING v4 04/16] fchroot01: test fchroot() with a directory fd Andrea Cervesato
2026-08-31  9:06   ` [LTP] syscalls: add v7.3 syscall numbers linuxtestproject.agent
2026-10-12 10:25   ` [LTP] [PATCH STAGING v4 04/16] fchroot01: test fchroot() with a directory fd Cyril Hrubis
2026-08-31  8:00 ` [LTP] [PATCH STAGING v4 05/16] fchroot02: test fchroot() invalid arguments Andrea Cervesato
2026-10-12 10:51   ` Cyril Hrubis
2026-08-31  8:00 ` [LTP] [PATCH STAGING v4 06/16] fchroot03: test fchroot() permission checks Andrea Cervesato
2026-10-12 10:32   ` Cyril Hrubis
2026-08-31  8:00 ` [LTP] [PATCH STAGING v4 07/16] fchroot04: test fchroot() into failfs as root Andrea Cervesato
2026-10-12 11:03   ` Cyril Hrubis
2026-08-31  8:00 ` [LTP] [PATCH STAGING v4 08/16] fchroot05: test failfs root can not be referenced Andrea Cervesato
2026-10-12 11:14   ` Cyril Hrubis
2026-08-31  8:00 ` [LTP] [PATCH STAGING v4 09/16] fchroot06: test path walks under failfs root Andrea Cervesato
2026-10-14 11:39   ` Cyril Hrubis
2026-08-31  8:00 ` [LTP] [PATCH STAGING v4 10/16] fchroot07: test execve blocked by " Andrea Cervesato
2026-10-13 15:44   ` Cyril Hrubis
2026-08-31  8:00 ` [LTP] [PATCH STAGING v4 11/16] fchroot08: test failfs root fork inheritance Andrea Cervesato
2026-10-13 16:02   ` Cyril Hrubis
2026-08-31  8:00 ` [LTP] [PATCH STAGING v4 12/16] fchroot09: test setns escape from failfs root Andrea Cervesato
2026-10-14 11:52   ` Cyril Hrubis
2026-08-31  8:00 ` [LTP] [PATCH STAGING v4 13/16] fchroot10: test failfs entry without no_new_privs Andrea Cervesato
2026-10-14 12:11   ` Cyril Hrubis
2026-08-31  8:00 ` [LTP] [PATCH STAGING v4 14/16] fchroot11: test failfs entry with no_new_privs Andrea Cervesato
2026-10-14 14:20   ` Cyril Hrubis [this message]
2026-08-31  8:00 ` [LTP] [PATCH STAGING v4 15/16] fchroot12: test failfs entry with shared fs_struct Andrea Cervesato
2026-10-14 15:10   ` Cyril Hrubis
2026-08-31  8:00 ` [LTP] [PATCH STAGING v4 16/16] fchroot13: test failfs entry when chrooted Andrea Cervesato

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=as-PxIfrUCyPZjQd@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=andrea.cervesato@suse.de \
    --cc=ltp@lists.linux.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox