Bug 1776096
Summary: | [rpc.statd] New use-after-free in monitor list when insertion fails for existing entry | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Yongcheng Yang <yoyang> |
Component: | nfs-utils | Assignee: | Steve Dickson <steved> |
Status: | CLOSED ERRATA | QA Contact: | Yongcheng Yang <yoyang> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 8.2 | CC: | gcase, pawel_sikora, rhandlin, steved, swhiteho, tborcin, xzhou |
Target Milestone: | rc | Keywords: | Regression, Reproducer |
Target Release: | 8.2 | Flags: | pm-rhel:
mirror+
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | nfs-utils-2.3.3-29.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-28 16:51:05 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1776036, 1776957 |
Description
Yongcheng Yang
2019-11-25 06:48:50 UTC
Since this is a regression, should it also be a blocker for 8.2? (In reply to Steve Whitehouse from comment #1) > Since this is a regression, should it also be a blocker for 8.2? It is a regression... since the permission denied broke. The fix is an easy one diff -up ./tests/nsm_client/nlm_sm_inter.h.orig ./tests/nsm_client/nlm_sm_inter.h diff -up ./utils/statd/monitor.c.orig ./utils/statd/monitor.c --- ./utils/statd/monitor.c.orig 2020-01-13 10:06:55.962136625 -0500 +++ ./utils/statd/monitor.c 2020-01-13 11:01:43.037265175 -0500 @@ -177,7 +177,6 @@ sm_mon_1_svc(struct mon *argp, struct sv * We're committed...ignoring errors. Let's hope that a malloc() * doesn't fail. (I should probably fix this assumption.) */ - clnt = NULL; if (!existing && !(clnt = nlist_new(my_name, mon_name, 0))) { free(dnsname); xlog_warn("out of memory"); So we need to fix this.... Waiting on the blocker ack. 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, 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-2020:1832 |