From: fujo <hooyan2024@gmail.com>
To: linux-fsdevel@vger.kernel.org
Cc: Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org, shaos <shawnq1@163.com>
Subject: [PATCH 1/2] fs: statmount: don't copy strings past the caller's buffer
Date: Wed, 21 Oct 2026 13:51:51 -0400 [thread overview]
Message-ID: <179260511193.411.4517720543579678364@gmail.com> (raw)
In-Reply-To: <179260511193.411.2849255769062027805@gmail.com>
statmount(2) collects all strings in a kernel buffer and copies them to
the user buffer after struct statmount. copy_statmount_to_user() copies
seq->count bytes at buf + sizeof(struct statmount), but only
statmount_string() checks whether they fit: it returns early when the
producer emitted nothing, before the size check.
If no producer emits anything -- for example STATMOUNT_MNT_UIDMAP on a
mount that is not idmapped -- the reserved empty string is the only
thing left in seq->buf. statmount(2) then copies that single NUL at
offset 512 even when the caller passed a smaller bufsize, and returns
success with size = 101 for bufsize = 100. The write is beyond the
buffer the caller declared; if the following page is unmapped the
syscall fails with EFAULT instead. The same request with a producer
that does emit data correctly returns EOVERFLOW.
Validate that the string area fits into s->bufsize before copying it
and return EOVERFLOW otherwise.
Reported-by: shaos <shawnq1@163.com>
Link: https://lore.kernel.org/all/20261020110747.959829-1-shawnq1@163.com/
Signed-off-by: fujo <hooyan2024@gmail.com>
---
fs/namespace.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/fs/namespace.c b/fs/namespace.c
index c30f06374..c8aceeff6 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -5831,8 +5831,18 @@ static int copy_statmount_to_user(struct kstatmount *s)
char __user *str = ((char __user *)s->buf) + sizeof(*sm);
size_t copysize = min_t(size_t, s->bufsize, sizeof(*sm));
- if (seq->count && copy_to_user(str, seq->buf, seq->count))
- return -EFAULT;
+ if (seq->count) {
+ /*
+ * The string area starts after the struct and must fit into the
+ * caller-provided buffer. A request that emitted no strings
+ * still leaves the reserved empty string in seq->buf.
+ */
+ if (s->bufsize < sizeof(*sm) ||
+ seq->count > s->bufsize - sizeof(*sm))
+ return -EOVERFLOW;
+ if (copy_to_user(str, seq->buf, seq->count))
+ return -EFAULT;
+ }
/* Return the number of bytes copied to the buffer */
sm->size = copysize + seq->count;
--
2.53.0
next prev parent reply other threads:[~2026-10-21 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 17:51 [PATCH 0/2] fs: two mount API fixes fujo
2026-10-21 17:51 ` fujo [this message]
2026-10-21 17:51 ` [PATCH 2/2] fs: reject U64_MAX cursors in listmount() and listns() fujo
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=179260511193.411.4517720543579678364@gmail.com \
--to=hooyan2024@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnq1@163.com \
--cc=viro@zeniv.linux.org.uk \
/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®