From: "Eric W. Biederman" <ebiederm@xmission.com>
To: Natasha Klaus <natalie.klaus@runtimeverification.com>
Cc: Christian Brauner <brauner@kernel.org>,
Kees Cook <kees@kernel.org>, Shuah Khan <shuah@kernel.org>,
Jeff Layton <jlayton@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] userns: reject out-of-range uid_map/gid_map values
Date: Wed, 07 Oct 2026 21:27:55 -0500 [thread overview]
Message-ID: <87se2h0vv8.fsf@email.froward.int.ebiederm.org> (raw)
In-Reply-To: <20260930112854.373184-1-natalie.klaus@runtimeverification.com> (Natasha Klaus's message of "Wed, 30 Sep 2026 14:28:52 +0300")
Natasha Klaus <natalie.klaus@runtimeverification.com> writes:
> map_write() silently truncates uid_map/gid_map/projid_map values above
> U32_MAX modulo 2^32 on 64-bit kernels, so e.g. "4294967301 1000 1" is
> installed as "5 1000 1" without an error. Patch 1 parses each field
> with kstrtou32() so such values fail with -EINVAL. Patch 2 adds
> selftests for out-of-range and negative values in each field and for
> the unchanged in-range path.
>
> This makes the parser more correct; it is not a security fix.
>
> The patch and the selftest were drafted by Claude Code (Claude Opus 5.5)
> in an interactive session; I reviewed, built and tested them. The
> assistant flagged the truncation while reading map_write(), and I
> confirmed it by writing to uid_map on a running kernel.
>
> Tested on v7.3-rc5-37-g551c722f4080 under virtme-ng, x86_64 defconfig
> with CONFIG_USER_NS: all 12 selftest cases pass on the patched kernel.
> On an unpatched 6.8 host the four above-u32 cases fail as expected,
> seven pass and the root-only case is skipped.
I don't see anything to object to in this one.
Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>
>
> Changes in v2:
> - Parse each field with kstrtou32() instead of simple_strtoull() plus a
> separate U32_MAX check (Eric W. Biederman).
> - Selftest: add negative values in each field, "0 <uid> 1", the
> largest valid first id, a line with extra spaces between fields, and
> the largest count written by a privileged parent (Eric W. Biederman).
> - Describe patch 1 as making the parser more correct, not as hardening.
> - Rebased onto v7.3-rc5-37-g551c722f4080.
>
> Link: https://lore.kernel.org/all/20260928072537.115668-1-natalie.klaus@runtimeverification.com/
>
> Natasha Klaus (2):
> userns: reject uid_map/gid_map values that do not fit in u32
> selftests/namespaces: add uid_map/gid_map range tests
>
> kernel/user_namespace.c | 29 +-
> tools/testing/selftests/namespaces/.gitignore | 1 +
> tools/testing/selftests/namespaces/Makefile | 3 +-
> .../selftests/namespaces/uid_map_range_test.c | 299 ++++++++++++++++++
> 4 files changed, 328 insertions(+), 4 deletions(-)
> create mode 100644 tools/testing/selftests/namespaces/uid_map_range_test.c
>
>
> base-commit: 551c722f40809618230001baccf219193e22fc5a
prev parent reply other threads:[~2026-10-08 3:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 11:28 Natasha Klaus
2026-09-30 11:28 ` [PATCH v2 1/2] userns: reject uid_map/gid_map values that do not fit in u32 Natasha Klaus
2026-09-30 11:28 ` [PATCH v2 2/2] selftests/namespaces: add uid_map/gid_map range tests Natasha Klaus
2026-10-08 2:27 ` Eric W. Biederman [this message]
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=87se2h0vv8.fsf@email.froward.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=brauner@kernel.org \
--cc=jlayton@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=natalie.klaus@runtimeverification.com \
--cc=shuah@kernel.org \
/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
all inboxes | Powered by JetHome®