From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Subject: [PATCH 0/4] fs: nfs: Fix buffer overflows
Date: Tue, 04 Nov 2025 09:08:04 +0100 [thread overview]
Message-ID: <20251104-nfs-v1-0-3e69e5c82a41@pengutronix.de> (raw)
The NFS does hardly any checks on incoming packets. It blindly trusts
the length values in packets and happily reads past the packets. This
series introduces a function to read from packets concentrating the
boundary checks in a single place. Also some other things I stumbled
upon along the way.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
Sascha Hauer (4):
fs: nfs: drop PROG_NFS special casing
fs: nfs: do not read past packets
fs: nfs: use dev_* for messages
fs: nfs: reduce unwanted message to debug level
fs/nfs.c | 379 ++++++++++++++++++++++++++++++++++++++++++++-------------------
1 file changed, 267 insertions(+), 112 deletions(-)
---
base-commit: 7605338da017da2492d83e919f7a88eefe4cd306
change-id: 20251104-nfs-0af879139539
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
next reply other threads:[~2025-11-04 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 8:08 Sascha Hauer [this message]
2025-11-04 8:08 ` [PATCH 1/4] fs: nfs: drop PROG_NFS special casing Sascha Hauer
2025-11-04 8:08 ` [PATCH 2/4] fs: nfs: do not read past packets Sascha Hauer
2025-11-04 8:08 ` [PATCH 3/4] fs: nfs: use dev_* for messages Sascha Hauer
2025-11-04 8:08 ` [PATCH 4/4] fs: nfs: reduce unwanted message to debug level 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=20251104-nfs-v1-0-3e69e5c82a41@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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