From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Cc: "Claude Opus 4.6 \(1M context\)" <noreply@anthropic.com>
Subject: [PATCH 1/2] fs: nfs: fix stack and packet buffer overflows from long NFS paths
Date: Thu, 02 Apr 2026 09:55:23 +0200 [thread overview]
Message-ID: <20260402-net-nfs-buffer-overflows-v1-1-5dc46ef1da81@pengutronix.de> (raw)
In-Reply-To: <20260402-net-nfs-buffer-overflows-v1-0-5dc46ef1da81@pengutronix.de>
nfs_mount_req() and nfs_umount_req() copy the NFS mount path into a
stack-allocated uint32_t data[1024] buffer (4096 bytes) with only ~40
bytes of RPC header overhead. A mount path longer than ~4056 characters
overflows the stack array.
Additionally, rpc_req() copies the data array into the PKTSIZE (1536)
packet buffer with only 1494 bytes available for UDP payload. After the
28-byte RPC call header, paths longer than ~1424 characters overflow
the packet buffer.
Fix by:
- Adding a path length check in nfs_mount_req() and nfs_umount_req()
against the stack buffer capacity before constructing the request
- Adding a payload size check in rpc_req() before the memcpy to the
packet buffer, protecting all RPC callers from overflows
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---
fs/nfs.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/fs/nfs.c b/fs/nfs.c
index 0b40c56ff3..edc15e0ce6 100644
--- a/fs/nfs.c
+++ b/fs/nfs.c
@@ -534,6 +534,13 @@ static struct packet *rpc_req(struct nfs_priv *npriv, int rpc_prog,
pkt.vers = hton32(3);
}
+ if (sizeof(pkt) + datalen * sizeof(uint32_t) >
+ PKTSIZE - ETHER_HDR_SIZE - sizeof(struct iphdr) - sizeof(struct udphdr)) {
+ dev_err(dev, "RPC request too large (%zu bytes)\n",
+ sizeof(pkt) + datalen * sizeof(uint32_t));
+ return ERR_PTR(-EMSGSIZE);
+ }
+
memcpy(payload, &pkt, sizeof(pkt));
memcpy(payload + sizeof(pkt), data, datalen * sizeof(uint32_t));
@@ -786,6 +793,11 @@ static int nfs_mount_req(struct nfs_priv *npriv)
pathlen = strlen(npriv->path);
+ if (pathlen > sizeof(data) - 11 * sizeof(uint32_t)) {
+ dev_err(dev, "path too long (%d bytes)\n", pathlen);
+ return -ENAMETOOLONG;
+ }
+
dev_dbg(dev, "%s: %s\n", __func__, npriv->path);
p = &(data[0]);
@@ -862,6 +874,8 @@ static void nfs_umount_req(struct nfs_priv *npriv)
struct packet *nfs_packet;
pathlen = strlen(npriv->path);
+ if (pathlen > sizeof(data) - 11 * sizeof(uint32_t))
+ return;
p = &(data[0]);
p = rpc_add_credentials(p);
--
2.47.3
next prev parent reply other threads:[~2026-04-02 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 7:55 [PATCH 0/2] nfs: protect against corrupt packets and userdata Sascha Hauer
2026-04-02 7:55 ` Sascha Hauer [this message]
2026-04-02 7:55 ` [PATCH 2/2] fs: nfs: fix NULL dereference in nfs_read_req on truncated packets Sascha Hauer
2026-04-02 10:39 ` Sascha Hauer
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=20260402-net-nfs-buffer-overflows-v1-1-5dc46ef1da81@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=noreply@anthropic.com \
/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