Fix one of the patches from the previous commit

- renamed variable caused failures in the QA runs
- Since teh variable is was used in an assert, the normal builds did not
  fail

Related: cve-2019-17543
This commit is contained in:
Jakub Martisko 2025-06-20 14:35:19 +02:00
parent 2b59416100
commit 9dd858e83d
2 changed files with 7 additions and 2 deletions

View File

@ -73,7 +73,7 @@ index 1e80c9812..461644da0 100644
*token += (BYTE)(matchCode);
}
+ /* Ensure we have enough space for the last literals. */
+ assert(!(outputDirective == fillOutput && op + 1 + LASTLITERALS > olimit));
+ assert(!(outputLimited == fillOutput && op + 1 + LASTLITERALS > olimit));
anchor = ip;

View File

@ -1,6 +1,6 @@
Name: lz4
Version: 1.8.3
Release: 4%{?dist}
Release: 5%{?dist}
Summary: Extremely fast compression algorithm
License: GPLv2+ and BSD
@ -84,6 +84,11 @@ chmod +x ./configure
%{_libdir}/liblz4.a
%changelog
* Fri Jun 20 2025 Jakub Martisko <jamartis@redhat.com> - 1.8.3-5
- Fix a renamed variable in one of the patches
- Since the variable was used in an assert, the regular build did not fail, but the QA builds did.
- Related: RHEL-87362
* Thu Jun 19 2025 Jakub Martisko <jamartis@redhat.com> - 1.8.3-4
- Fix CVE-2019-17543
- Resolves: RHEL-87362