From: Prasanth R <ragaprasanth@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: yoann.congal@smile.fr, Prasanth R <ragaprasanth@gmail.com>
Subject: [scarthgap][PATCH 1/2] u-boot: fix CVE-2026-29009
Date: Tue, 17 Nov 2026 16:38:48 +0900 [thread overview]
Message-ID: <20261117073849.3089566-1-ragaprasanth@gmail.com> (raw)
A malicious NFS server can overflow nfs_path_buff with READLINK
replies. Backport the upstream fix, as done for wrynose. It applies
to 2024.01 unchanged.
AI-Generated: Uses Claude
Signed-off-by: Prasanth R <prasanth.r@lineo.co.jp>
---
Tested: built with CONFIG_CMD_NFS=y for qemux86-64. Also ran
nfs_readlink_reply() from the unpatched and patched 2024.01 source
under AddressSanitizer with two 1100-byte READLINK replies: without
this patch it overflows nfs_path_buff, with it the second reply is
dropped.
.../u-boot/files/CVE-2026-29009.patch | 53 +++++++++++++++++++
meta/recipes-bsp/u-boot/u-boot_2024.01.bb | 1 +
2 files changed, 54 insertions(+)
create mode 100644 meta/recipes-bsp/u-boot/files/CVE-2026-29009.patch
diff --git a/meta/recipes-bsp/u-boot/files/CVE-2026-29009.patch b/meta/recipes-bsp/u-boot/files/CVE-2026-29009.patch
new file mode 100644
index 0000000000..35f168005e
--- /dev/null
+++ b/meta/recipes-bsp/u-boot/files/CVE-2026-29009.patch
@@ -0,0 +1,53 @@
+From d6694018eaddefac6aae974f9cec72fd6e58f1bc Mon Sep 17 00:00:00 2001
+From: Sebastian Josue Alba Vives <sebasjosue84@gmail.com>
+Date: Thu, 9 Apr 2026 10:44:40 -0600
+Subject: [PATCH] net: nfs: fix buffer overflow in nfs_readlink_reply()
+
+nfs_readlink_reply() validates rlen only against the incoming packet
+length (inherited from CVE-2019-14195), but not against the destination
+buffer nfs_path_buff[2048]. A malicious NFS server can send a valid
+READLINK reply where pathlen + rlen exceeds sizeof(nfs_path_buff),
+overflowing the BSS buffer into adjacent memory.
+
+The recent fix in fd6e3d34097f addressed the same overflow class in
+net/lwip/nfs.c but left the legacy path in net/nfs-common.c unpatched.
+
+Add bounds checks before both memcpy calls in nfs_readlink_reply():
+- relative path branch: reject if pathlen + rlen >=
+ sizeof(nfs_path_buff)
+- absolute path branch: reject if rlen >= sizeof(nfs_path_buff)
+
+Fixes: cf3a4f1e86 ("net: nfs: Fix CVE-2019-14195")
+
+CVE: CVE-2026-29009
+
+Upstream-Status: Backport [https://git.u-boot-project.org/u-boot/u-boot/-/commit/d6694018eaddefac6aae974f9cec72fd6e58f1bc]
+
+Cc: stable@vger.kernel.org
+Signed-off-by: Sebastian Alba Vives <sebasjosue84@gmail.com>
+Reviewed-by: Jerome Forissier <jerome.forissier@arm.com>
+Signed-off-by: Roopa Kalmath <Roopa.Kalmath@windriver.com>
+---
+ net/nfs.c | 4 ++++
+ 1 file changed, 4 insertions(+)
+
+diff --git a/net/nfs.c b/net/nfs.c
+index 537d4c62..9b628ecf 100644
+--- a/net/nfs.c
++++ b/net/nfs.c
+@@ -698,11 +698,15 @@ static int nfs_readlink_reply(uchar *pkt, unsigned len)
+
+ strcat(nfs_path, "/");
+ pathlen = strlen(nfs_path);
++ if (pathlen + rlen >= sizeof(nfs_path_buff))
++ return -NFS_RPC_DROP;
+ memcpy(nfs_path + pathlen,
+ (uchar *)&(rpc_pkt.u.reply.data[2 + nfsv3_data_offset]),
+ rlen);
+ nfs_path[pathlen + rlen] = 0;
+ } else {
++ if (rlen >= sizeof(nfs_path_buff))
++ return -NFS_RPC_DROP;
+ memcpy(nfs_path,
+ (uchar *)&(rpc_pkt.u.reply.data[2 + nfsv3_data_offset]),
+ rlen);
diff --git a/meta/recipes-bsp/u-boot/u-boot_2024.01.bb b/meta/recipes-bsp/u-boot/u-boot_2024.01.bb
index 7eaeed1004..6aa98e1740 100644
--- a/meta/recipes-bsp/u-boot/u-boot_2024.01.bb
+++ b/meta/recipes-bsp/u-boot/u-boot_2024.01.bb
@@ -13,4 +13,5 @@ SRC_URI += "file://CVE-2024-57254.patch \
file://CVE-2024-57259.patch \
file://CVE-2024-42040.patch \
file://CVE-2026-46728.patch \
+ file://CVE-2026-29009.patch \
"
--
2.34.1
next reply other threads:[~2026-11-17 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 7:38 Prasanth R [this message]
2026-11-17 7:38 ` [scarthgap][PATCH 2/2] u-boot-tools: ignore CVE-2026-29007, CVE-2026-29008 and CVE-2026-29009 Prasanth R
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=20261117073849.3089566-1-ragaprasanth@gmail.com \
--to=ragaprasanth@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yoann.congal@smile.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.