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.

Bug 1555281

Summary: backport fix for libnm wrongly not cancelling async operations
Product: Red Hat Enterprise Linux 7 Reporter: Thomas Haller <thaller>
Component: NetworkManagerAssignee: Thomas Haller <thaller>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.5CC: atragler, bberg, bgalvani, fgiudici, fpokryvk, lrintel, rkhan, sukulkar, thaller, vbenes
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.12.0-0.1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 11:11:28 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:

Description Thomas Haller 2018-03-14 12:06:29 UTC 
A user of libnm who passes a GCancellable to async operations, requires that the result is cancelled when he cancels the GCancellable.

Otherwise, the contract of th async operation is violated, and the caller might wrongly assume that the operation was not cancelled, when in fact it was. That might lead for example to use-after-free crashes.

Backport upstream fix https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=26c215e22dcfff9e61a58e9348991ed77c3f8861


See also  https://bugzilla.gnome.org/show_bug.cgi?id=794088



The severity of the bug depends on whether there are users of libnm who encounter this broken behavior.
Comment 2 Thomas Haller 2018-03-14 12:10:27 UTC 
See also: https://developer.gnome.org/gio/stable/GSimpleAsyncResult.html#g-simple-async-result-set-check-cancellable


This bug is present in libnm since the beginning.

As said, the severity depends on uses who rely on being able to cancel the request (and whether the trust libnm on the response).
Comment 3 Benjamin Berg 2018-03-14 13:01:24 UTC 
For context. The only known user who is affected by this is control-center. This bug fixes a potential crasher if the user quickly switches away from the network configuration pane.
Comment 6 errata-xmlrpc 2018-10-30 11:11:28 UTC 
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-2018:3207