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 0/2] nfs: protect against corrupt packets and userdata
Date: Thu, 02 Apr 2026 09:55:22 +0200 [thread overview]
Message-ID: <20260402-net-nfs-buffer-overflows-v1-0-5dc46ef1da81@pengutronix.de> (raw)
One patch protecting against a too long mount path and one against
truncated packets.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
Sascha Hauer (2):
fs: nfs: fix stack and packet buffer overflows from long NFS paths
fs: nfs: fix NULL dereference in nfs_read_req on truncated packets
fs/nfs.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
---
base-commit: 0933e8f2ebf0d91dfcf177a4e4292b02921a53f1
change-id: 20260402-net-nfs-buffer-overflows-48255656eefe
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
next reply other threads:[~2026-04-02 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 7:55 Sascha Hauer [this message]
2026-04-02 7:55 ` [PATCH 1/2] fs: nfs: fix stack and packet buffer overflows from long NFS paths Sascha Hauer
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-0-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