CWE data temporarily unavailableCWE data is currently experiencing intermittent outages, which may cause incomplete section loading on CVE pages. We are actively working on a fix.

CVE-2026-76642

Description

When an external mount. helper runs but exits with a nonzero status, libmount still treats the helper invocation as successful and runs privileged post-mount hooks. A local unprivileged user with an /etc/fstab entry that uses the user option together with X-mount.idmap or X-mount.owner/group/mode can cause those hooks to clone or re-own the underlying filesystem after the helper fails, leading to local privilege escalation.

Statement

A flaw was found in the util-linux libmount library, which Red Hat rates as Important severity. When an external mount. helper executes but exits with a nonzero status, libmount incorrectly treats the helper invocation as successful and runs privileged MNT_STAGE_MOUNT_POST hooks (X-mount.idmap, X-mount.owner/group/mode) as if the requested filesystem had been mounted. A local unprivileged user who can trigger a mount defined by a root-controlled /etc/fstab entry combining the user option with X-mount.idmap or X-mount.owner/group/mode can abuse this to escalate privileges: with X-mount.idmap, the idmap post-hook clones the pre-existing filesystem under the target, inheriting suid and exec flags from the underlying mount, which can allow the user to obtain EUID 0; independently, X-mount.owner/group/mode post-hooks can change ownership and mode of the physical target inode even when no mount was created. Exploitation requires the SUID-root mount(8) binary, a root-controlled user-mountable fstab entry with those X-mount.* options, and an external helper that exits nonzero; the helper itself need not be malicious. This flaw affects the util-linux component in Red Hat Enterprise Linux 10, Red Hat In-Vehicle OS, Red Hat Hardened Images, and certain container images, as well as Fedora in the community stream, where fixes are being pursued by the responsible engineering teams. Red Hat Enterprise Linux 7, 8, and 9, and Red Hat Enterprise Linux CoreOS (OpenShift Container Platform) are not affected because the vulnerable code is not present in their util-linux versions. Red Hat assigns this flaw a CVSS 3.1 base score of 7.8, while the upstream CVSS 4.0 score is 8.5; both place the flaw within Important severity. This issue is distinct from CVE-2026-53612, which involves a time-of-check race condition in the same post-hook code, whereas this flaw involves no race or path substitution.

Mitigation

Avoid combining the user (or users) fstab option with X-mount.idmap or X-mount.owner/group/mode on entries that invoke an external mount.<type> helper. Administrators can also remove or restrict user-mountable fstab entries that specify those X-mount.* options.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.8N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Red Hat CVSS v3 Score Explanation

Deterministic local privilege escalation after a failed external mount helper; no race. Requires a user-mountable fstab entry with X-mount.idmap or X-mount.owner/group/mode. AC:L because exploitation does not depend on winning a race once those options are present.

Acknowledgements

Red Hat would like to thank Andreas Gabriel Berbescu (Independent Security Researcher) and Iván Redondo Plaza (Independent Security Researcher) for reporting this issue.

Frequently Asked Questions

Want to get errata notifications? Sign up here.