Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This bug was initially created as a copy of Bug #2167803
I am copying this bug because:
Description of problem:
Issue reported by Ilya Leoshkevich from IBM
The tests pass, but fuzzing finds something:
==290951==ERROR: AddressSanitizer: SEGV on unknown address
0x62d100000000 (pc 0x0000011806be bp 0x03ffffff5a70 sp 0x03ffffff5a70
T0)
==290951==The signal is caused by a UNKNOWN memory access.
#0 0x11806be in fill_window /home/iii/zlib-fuzz/build/zlib/build-
libfuzzer/deflate.c:1604:24
#1 0x119d31f in deflate_fast /home/iii/zlib-fuzz/build/zlib/build-
libfuzzer/deflate.c:1902:13
#2 0x118e60f in deflate /home/iii/zlib-fuzz/build/zlib/build-
libfuzzer/deflate.c:1066:18
#3 0x1174983 in Deflate /home/iii/zlib-fuzz/fuzz_target.cpp:250:13
#4 0x1174983 in RunDeflateOp /home/iii/zlib-
fuzz/fuzz_target.cpp:795:15
#5 0x1174983 in ExecutePlan /home/iii/zlib-
fuzz/fuzz_target.cpp:1006:5
#6 0x1174983 in LLVMFuzzerTestOneInput /home/iii/zlib-
fuzz/fuzz_target.cpp:1075:3
Ilya also found a fix for this issue that has been committed by upstream author:
https://github.com/madler/zlib/commit/2d80d3f6b52f9fa454c26c89d2d6a1790e1cecb0
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (zlib bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:7115