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.
(In reply to Richard Guy Briggs from comment #10)
> After converting "syscall(__NR_mmap, " to "mmap(" and adding its "#include
> <sys/mman.h>" header file, it compiles and runs without segfault or panic.
> The modified source is in repro-s390x.c on that system.
Thanks! I'll give that a try.
BTW I just realized I pasted the link to a different version of the reproducer earlier in comment#7.
The one used in testing was actually https://syzkaller.appspot.com/x/repro.c?x=1648fe09e00000
Sorry for the confusion.
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 (Moderate: kernel security, 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/RHSA-2020:4431
Comment 16Frantisek Hrbata
2021-01-31 19:42:19 UTC
*** Bug 1921037 has been marked as a duplicate of this bug. ***
Comment 17Richard Guy Briggs
2021-02-01 17:45:36 UTC
*** Bug 1921040 has been marked as a duplicate of this bug. ***
Description of problem: syzbot found two crashers in audit reported on the upstream linux-audit mailing list: - KMSAN: uninit-value in audit_receive [1] - fix posted [3] 756125289285 ("audit: always check the netlink payload length in audit_receive_msg()") - kernel BUG at arch/x86/mm/physaddr.c:LINE! (4) [2] - fix posted [4] 2ad3e17ebf94 ("audit: fix error handling in audit_data_to_entry()") Both fixes have been tagged for the upstream stable branch. Version-Release number of selected component (if applicable): RHEL8.2 How reproducible: See syzbot reports Steps to Reproduce: 1. See syzbot reports 2. 3. Actual results: Kernel is caused to crash. Expected results: Kernel doesn't crash. Additional info: [1] - https://www.redhat.com/archives/linux-audit/2020-February/msg00091.html [2] - https://www.redhat.com/archives/linux-audit/2020-February/msg00087.html [3] - https://www.redhat.com/archives/linux-audit/2020-February/msg00104.html [4] - https://www.redhat.com/archives/linux-audit/2020-February/msg00094.html