From: Peter Marko <peter.marko@siemens.com>
To: openembedded-core@lists.openembedded.org
Cc: Peter Marko <peter.marko@siemens.com>
Subject: [OE-core][PATCH] nfs-utils: upgrade 2.8.5 -> 2.8.6
Date: Thu, 12 Mar 2026 21:04:48 +0100 [thread overview]
Message-ID: <20260312200448.2019165-1-peter.marko@siemens.com> (raw)
From: Peter Marko <peter.marko@siemens.com>
Fixes CVE-2025-12801 per [1].
[1] https://security-tracker.debian.org/tracker/CVE-2025-12801
Signed-off-by: Peter Marko <peter.marko@siemens.com>
---
.../nfs-utils/{nfs-utils_2.8.5.bb => nfs-utils_2.8.6.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-connectivity/nfs-utils/{nfs-utils_2.8.5.bb => nfs-utils_2.8.6.bb} (98%)
diff --git a/meta/recipes-connectivity/nfs-utils/nfs-utils_2.8.5.bb b/meta/recipes-connectivity/nfs-utils/nfs-utils_2.8.6.bb
similarity index 98%
rename from meta/recipes-connectivity/nfs-utils/nfs-utils_2.8.5.bb
rename to meta/recipes-connectivity/nfs-utils/nfs-utils_2.8.6.bb
index 119e49e2a2..7c2b0078d0 100644
--- a/meta/recipes-connectivity/nfs-utils/nfs-utils_2.8.5.bb
+++ b/meta/recipes-connectivity/nfs-utils/nfs-utils_2.8.6.bb
@@ -25,7 +25,7 @@ SRC_URI = "${KERNELORG_MIRROR}/linux/utils/nfs-utils/${PV}/nfs-utils-${PV}.tar.x
file://0005-find-OE-provided-Kerberos.patch \
"
-SRC_URI[sha256sum] = "b13ca4a9df44186bdbe107514b22732d4243f785f95daf2fb86afc1edba15bbb"
+SRC_URI[sha256sum] = "2bd7b34e809a7eff2f4bc5fc5fd96ebcd66a5458b471a270cbd2dc169b011550"
# Only kernel-module-nfsd is required here (but can be built-in) - the nfsd module will
# pull in the remainder of the dependencies.
next reply other threads:[~2026-03-12 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 20:04 Peter Marko [this message]
2026-03-13 10:32 ` [OE-core][PATCH] nfs-utils: upgrade 2.8.5 -> 2.8.6 Mathieu Dubois-Briand
2026-03-14 21:37 ` Marko, Peter
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=20260312200448.2019165-1-peter.marko@siemens.com \
--to=peter.marko@siemens.com \
--cc=openembedded-core@lists.openembedded.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