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 clone of Bug #2209676 +++
Description of problem:
valgrind errors on openscap memcheck, see the reproducer below. Snip of the log with error (full valgrind output (valgrind.out) is attached):
==33335== Memcheck, a memory error detector
==33335== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==33335== Using Valgrind-3.21.0 and LibVEX; rerun with -h for copyright info
==33335== Command: oscap oval eval rpmverifyfile.oval.xml
==33335==
==33335== Thread 4 input_handler:
==33335== realloc() with size 0
==33335== at 0x4849A40: realloc (vg_replace_malloc.c:1649)
==33335== by 0x495A9CA: UnknownInlinedFun (seap-packet.c:209)
==33335== by 0x495A9CA: SEAP_packet_recv.isra.0 (seap-packet.c:730)
==33335== by 0x4931403: SEAP_recvmsg (seap.c:360)
==33335== by 0x4934034: probe_input_handler (input_handler.c:102)
==33335== by 0x4A57831: start_thread (in /usr/lib64/libc.so.6)
==33335== by 0x49F7313: clone (in /usr/lib64/libc.so.6)
==33335== Address 0x7e44fe0 is 0 bytes after a block of size 0 alloc'd
==33335== at 0x484482F: malloc (vg_replace_malloc.c:431)
==33335== by 0x495A40F: UnknownInlinedFun (seap-packet.c:110)
==33335== by 0x495A40F: SEAP_packet_recv.isra.0 (seap-packet.c:730)
==33335== by 0x4931403: SEAP_recvmsg (seap.c:360)
==33335== by 0x4934034: probe_input_handler (input_handler.c:102)
==33335== by 0x4A57831: start_thread (in /usr/lib64/libc.so.6)
==33335== by 0x49F7313: clone (in /usr/lib64/libc.so.6)
==33335==
Error:
unknown error code 14
Memcheck: the 'impossible' happened:
unknown error code in mc_eq_Error
...
Version-Release number of selected component (if applicable):
valgrind-3.21.0-2.el8.x86_64
openscap-1.3.7-1.el8.x86_64
How reproducible:
deterministic
Steps to Reproduce:
1. dnf -y install openscap-scanner valgrind
2. dnf -y debuginfo-install openscap
3. valgrind --leak-check=full oscap oval eval rpmverifyfile.oval.xml &>valgrind.out
Note: Tested on RHEL-8.9.0-20230521.41 compose, error occurs also without `--leak-check=full` parameter. File rpmverifyfile.oval.xml is attached.
Actual results:
valgrind errors on openscap memcheck with "unknown error code 14".
Expected results:
valgrind successfully performs openscap memcheck.
Additional info:
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 (valgrind 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:6953