Skip to content
statance
MenuClose
Log inStart for free ↗
high · CVSS 7.8

CVE-2026-78410

Util-linux: util-linux: restricted bind mounts do not pin the source, allowing x-mount.owner/group/mode redirection

Published 2 Sept 2026 · Source updated 5 Nov 2026 · Retrieved 2026-11-05 03:16 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

A flaw was found in util-linux. Restricted bind mounts take the source path from fstab but do not pin that source before the privileged mount. A local unprivileged user who can replace the authorized source or a writable ancestor can redirect SUID mount(8) to bind another host directory. If the fstab entry also sets X-mount.owner, X-mount.group, or X-mount.mode, root then changes ownership or mode on that redirected inode.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
util-linuxRed Hatunaffected: 0:2.40.2-18.el10_2.20 to < *See vendor advisory
costmanagement/costmanagement-ui-rhel10Red Hatunaffected: 1793825318 to < *See vendor advisory
util-linux-mainRed Hatunaffected: 2.42.2-3.4.hum1 to < *See vendor advisory
util-linuxRed HatDefault status: unaffectedSee vendor advisory
util-linuxRed HatDefault status: unaffectedSee vendor advisory
rhel8/flatpak-runtimeRed HatDefault status: unaffectedSee vendor advisory
rhel8/flatpak-sdkRed HatDefault status: unaffectedSee vendor advisory
util-linuxRed HatDefault status: unaffectedSee vendor advisory
openshift/ose-rhel-coreos-8Red HatDefault status: unaffectedSee vendor advisory
openshift/ose-rhel-coreos-9Red HatDefault status: unaffectedSee vendor advisory
openshift/ose-rhel-coreos-9Red HatDefault status: unaffectedSee vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed