Medium [CVE-2026-54370] TOCTOU Symlink Traversal via getfacl/setfacl
This medium-severity Red Hat Linux advisory covers CVE-2026-54370 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
acl before version 2.4.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link between an lstat() check and subsequent symlink-following operations such as stat(), chown(), chmod(), acl_get_file(), and acl_set_file().
Attackers who control a pathname component can redirect file access control list operations to arbitrary files when getfacl, setfacl, or chacl is invoked by a privileged process over an attacker-controlled path, resulting in local privilege escalation.
By replacing a pathname component with a symbolic link between a security check and subsequent file operations, an attacker can redirect file access control list operations. Red Hat severity: Moderate — CVSS 6.3 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N).
Weakness: CWE-367.
Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat Discovery 2; Red Hat Hardened Images; Red Hat Insights proxy 1.5; Red Hat OpenShift distributed tracing 3.10.2; Red Hat Update Infrastructure 5; Red Hat Enterprise Linux 6; Red Hat Enterprise Linux 7; Red Hat OpenShift Container Platform 4.
Affected products named by the advisory: Red Hat package: acl.
- < 2.4.0
Official advisory · high-confidence parse· fetched 14 days ago·verify at source
- acl-0:2.4.0-1.el10_2
- acl-0:2.4.0-1.el8_10
- acl-0:2.4.0-1.el9_8
- discovery/discovery-ui-rhel9:1784821750
- acl-main-2.4.0-0.1.hum1
- insights-proxy/insights-proxy-container-rhel9:1786433656
- rhosdt/opentelemetry-collector-rhel9:1785704636
- rhui5/cds-kubernetes-rhel9:1784794818
- rhui5/cds-rhel9:1784794778
- rhui5/haproxy-rhel9:1784795112
- rhui5/installer-rhel9:1784794289
- rhui5/rhua-rhel9:1784795076
- rhui5/cds-kubernetes-tp-rhel9:1787241211
- rhui5/installer-tp-rhel9:1787135742
- rhui5/rhua-tp-rhel9:1787241260
- RHSA-2026:42739
- RHSA-2026:43420
- RHSA-2026:42736
- RHSA-2026:46836
- RHSA-2026:34351
- RHSA-2026:53371
- RHSA-2026:50205
- RHSA-2026:44481
- RHSA-2026:58981
Official advisory · high-confidence parse· fetched 14 days ago·verify at source
Mitigation
Upgrade to a fixed release: acl-0:2.4.0-1.el10_2, acl-0:2.4.0-1.el8_10, acl-0:2.4.0-1.el9_8, discovery/discovery-ui-rhel9:1784821750, acl-main-2.4.0-0.1.hum1, insights-proxy/insights-proxy-container-rhel9:1786433656. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 14 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.