Skip to content
Fencer Intel
low 3.3

CVE-2011-0542 json

fusermount in fuse 2.8.5 and earlier does not perform a chdir to / before performing a mount or umount, which allows local users to unmount…

published 2011-09-02 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-0560

cvss
3.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 25%
public exploits
0
none known

Summary

fusermount in fuse 2.8.5 and earlier does not perform a chdir to / before performing a mount or umount, which allows local users to unmount arbitrary directories via unspecified vectors.

Patch / fix

  • fuse Debian 13, Debian 12 2.8.5-1

debian advisories DEBIAN-CVE-2011-0542

  • fuse RHEL 6 2.8.3-3.el6_1
  • fuse-libs RHEL 6 2.8.3-3.el6_1

red hat advisories RHSA-2011:1083

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-0542 updated cvss 2.6

fuse: unprivileged user can unmount arbitrary locations via symlink attack

  • Red Hat Enterprise Linux 5 fuse, util-linux
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 6 uuidd, libuuid, libblkid, util-linux-ng
    affected: no fix available
  • Red Hat Enterprise Linux Server (v. 6) fuse 2.8.3-3.el6_1, fuse-libs 2.8.3-3.el6_1
    fixed: vendor fix RHSA-2011:1083

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 3.3 AV:L/AC:M/Au:N/C:N/I:P/A:P

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.