Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1451820 - "setfacl --restore" fails due to use of uninitialized memory [el7]
Summary: "setfacl --restore" fails due to use of uninitialized memory [el7]
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: acl
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: Eva Mrakova
Depends On: 1451826
Blocks: 1420851 1465901 1466365 1451801
TreeView+ depends on / blocked
Reported: 2017-05-17 15:07 UTC by Kamil Dudka
Modified: 2020-09-10 10:35 UTC (History)
5 users (show)

Fixed In Version: acl-2.2.51-14.el7
Doc Type: No Doc Update
Doc Text:
Clone Of: 1451801
: 1451826 (view as bug list)
Last Closed: 2018-04-10 13:13:40 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0772 0 None None None 2018-04-10 13:13:59 UTC

Description Kamil Dudka 2017-05-17 15:07:30 UTC
+++ This bug was initially created as a clone of Bug #1451801 +++

Description of problem:

When using "setfacl --restore <aclfile>" command, the command may fail when setting ACLs because of the reading of unitialized memory, causing unexpected code path to be executed.

Requesting backport of

Version-Release number of selected component (if applicable):


How reproducible:

Always on customer setup, never on mine.

Additional info:

Backporting fixed the issue.

--- Additional comment from Kamil Dudka on 2017-05-17 16:59:31 CEST ---

As discussed privately, this is easy and safe to backport.  Moreover, the fix is already verified in customer's environment.

Comment 11 errata-xmlrpc 2018-04-10 13:13:40 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.

Note You need to log in before you can comment on or make changes to this bug.