Strix
26.1K

CVE-2014-5207

UnknownEPSS 0.89%

Last modified

CVE-2014-5207 is a vulnerability of currently unknown severity. fs/namespace.c in the Linux kernel through 3.16.1 does not properly restrict clearing MNT_NODEV, MNT_NOSUID, and MNT_NOEXEC and changing MNT_ATIME_MASK during a remount of a bind mount, which allows local users to gain privileges, interfere with backups and auditing on systems that had atime enabled, or cause a denial of service (excessive filesystem updating) on systems that had atime disabled via a "mount -o remount" command within a user namespace.. EPSS estimates a 0.89% chance of exploitation in the next 30 days.

Description

fs/namespace.c in the Linux kernel through 3.16.1 does not properly restrict clearing MNT_NODEV, MNT_NOSUID, and MNT_NOEXEC and changing MNT_ATIME_MASK during a remount of a bind mount, which allows local users to gain privileges, interfere with backups and auditing on systems that had atime enabled, or cause a denial of service (excessive filesystem updating) on systems that had atime disabled via a "mount -o remount" command within a user namespace.

Metrics

EPSS Probability
0.89%

54.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
LinuxLinux Kernel<= 3.16.1
CanonicalUbuntu Linux12.04
CanonicalUbuntu Linux14.04

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2014-5207?
fs/namespace.c in the Linux kernel through 3.16.1 does not properly restrict clearing MNT_NODEV, MNT_NOSUID, and MNT_NOEXEC and changing MNT_ATIME_MASK during a remount of a bind mount, which allows local users to gain privileges, interfere with backups and auditing on systems that had atime enabled, or cause a denial of service (excessive filesystem updating) on systems that had atime disabled via a "mount -o remount" command within a user namespace.
How severe is CVE-2014-5207?
Severity scoring for CVE-2014-5207 is pending analysis. The EPSS model estimates a 0.89% probability of exploitation in the next 30 days.
How do I fix CVE-2014-5207?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2014-5207?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST