public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Xavier Bachelot <xavier@bachelot.org>
To: git-commits@fedoraproject.org
Subject: [rpms/libnfs] epel8: Add upstream patch for CVE-2026-53689
Date: Wed, 12 Aug 2026 23:05:40 GMT	[thread overview]
Message-ID: <178657594037.1.2670602251068928944.rpms-libnfs-9181fcf0bc30@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/libnfs
Branch : epel8
Commit : 9181fcf0bc30fcab6f9a079c08b799a1d14bb66c
Author : Xavier Bachelot <xavier@bachelot.org>
Date   : 2026-08-13T00:58:15+02:00
Stats  : +36/-1 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/libnfs/c/9181fcf0bc30fcab6f9a079c08b799a1d14bb66c?branch=epel8

Log:
Add upstream patch for CVE-2026-53689

---
diff --git a/libnfs-6.0.2-CVE-2026-53689.patch b/libnfs-6.0.2-CVE-2026-53689.patch
new file mode 100644
index 0000000..7fb368b
--- /dev/null
+++ b/libnfs-6.0.2-CVE-2026-53689.patch
@@ -0,0 +1,28 @@
+From 55c18ea33a83d667f79f0ef209c96895795c729f Mon Sep 17 00:00:00 2001
+From: Ronnie Sahlberg <ronniesahlberg@gmail.com>
+Date: Wed, 10 Jun 2026 11:43:28 +1000
+Subject: [PATCH] ZDR: check the string size for sanity
+
+It could otherwise cause an overflow in the bounds check later.
+
+Reported-by: Nick Hummel <nickhummel@google.com>
+Signed-off-by: Ronnie Sahlberg <ronniesahlberg@gmail.com>
+---
+ lib/libnfs-zdr.c | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/lib/libnfs-zdr.c b/lib/libnfs-zdr.c
+index 2945dc49..357b2746 100644
+--- a/lib/libnfs-zdr.c
++++ b/lib/libnfs-zdr.c
+@@ -318,7 +318,9 @@ bool_t libnfs_zdr_string(ZDR *zdrs, char **strp, uint32_t maxsize)
+ 	if (!libnfs_zdr_u_int(zdrs, &size)) {
+ 		return FALSE;
+ 	}
+-
++	if (size > zdrs->size) {
++		return FALSE;
++	}
+ 	if (zdrs->pos + (int)size > zdrs->size) {
+ 		return FALSE;
+ 	}

diff --git a/libnfs.spec b/libnfs.spec
index 72d0ad1..c9e9e2a 100644
--- a/libnfs.spec
+++ b/libnfs.spec
@@ -1,12 +1,15 @@
 Name:		libnfs
 Version:	4.0.0
-Release:	1%{?dist}
+Release:	2%{?dist}
 Summary:	Client library for accessing NFS shares over a network
 # The library is licensed as LGPLv2+, the protocol definition is BSD
 License:	LGPLv2+ and BSD
 URL:		https://github.com/sahlberg/libnfs
 Source0:	%{url}/archive/%{name}-%{version}/%{name}-%{version}.tar.gz
 
+# https://github.com/sahlberg/libnfs/commit/55c18ea33a83d667f79f0ef209c96895795c729f
+Patch2:         libnfs-6.0.2-CVE-2026-53689.patch
+
 BuildRequires:	gcc
 BuildRequires:	automake
 BuildRequires:	libtool
@@ -45,6 +48,7 @@ NFS servers using libnfs.
 
 %prep
 %setup -q -n %{name}-%{name}-%{version}
+%patch -P2 -p1
 autoreconf -vif
 
 %build
@@ -78,6 +82,9 @@ rm -f %{buildroot}%{_libdir}/*.la
 %{_mandir}/man1/nfs-*.1*
 
 %changelog
+* Mon Aug 10 2026 Xavier Bachelot <xavier@bachelot.org> - 4.0.0-2
+- Add upstream patch for CVE-2026-53689
+
 * Wed Sep 11 2019 Leigh Scott <leigh123linux@googlemail.com> - 4.0.0-1
 - Update to 4.0.0
 

                 reply	other threads:[~2026-08-12 23:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178657594037.1.2670602251068928944.rpms-libnfs-9181fcf0bc30@fedoraproject.org \
    --to=xavier@bachelot.org \
    --cc=git-commits@fedoraproject.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