CVE-2014-1874: Input Validation

Published Feb 6, 2014
·
Updated

Last updated 24 July 2024

Other sources

Linux kernel built with the NSA SELinux Support(CONFIGSECURITYSELINUX) is vulnerable to a crash caused by an empty SELinux security context value. If a file has an empty security context, listing it via 'ls(1)' could trigger this crash. Only user/processes with CAPMACADMIN privileges are allowed to set the SELinux security context of a file.

A user/process with CAPMACADMIN privileges could use this flaw to crash the kernel, resulting in a DoS.

Upstream fix: ------------- -> http://marc.info/?l=selinux&m=139110025203759&w=2

Red Hat

The securitycontexttosidcore function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAPMACADMIN capability to set a zero-length security context.

Launchpad

Affected Software

7 affected componentsFixes available
Linux Linux kernel<3.13.4
SUSE Linux Enterprise Server=10-sp4
Canonical Ubuntu Linux=10.04
Canonical Ubuntu Linux=12.04
Canonical Ubuntu Linux=12.10
Canonical Ubuntu Linux=13.10
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.13.4
  3. Compensating control

    Avoid allowing untrusted users/processes to obtain CAP_MAC_ADMIN privileges on systems with NSA SELinux Support (CONFIG_SECURITY_SELINUX), since CAP_MAC_ADMIN is required to set a zero-length/empty SELinux security context that triggers the kernel crash.

Event History

Feb 6, 2014
Data Sourced
via Red Hat·05:39 PM
DescriptionSeverityAffected Software
Feb 28, 2014
CVE Published
via MITRE·02:00 AM
Data Sourced
via MITRE·02:00 AM
Description
Jan 11, 2024
Data Sourced
via Launchpad·10:04 PM
Description
Sep 16, 2024
Data Sourced
via Ubuntu·01:03 AM
RemedyDescriptionSeverityAffected Software
Apr 28, 2025
Data Sourced
via Debian·02:09 AM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2014-1874?

CVE-2014-1874 is considered to have a high severity due to its potential to cause a crash in the Linux kernel.

2

How do I fix CVE-2014-1874?

To fix CVE-2014-1874, update the Linux kernel to version 5.10.223-1 or later, or ensure your system is running a patched version.

3

Which versions of Linux are affected by CVE-2014-1874?

CVE-2014-1874 affects multiple versions, including specific versions of Ubuntu and SUSE Linux, as well as any Linux kernel before 3.13.4.

4

Can exploiting CVE-2014-1874 lead to unauthorized access?

Exploiting CVE-2014-1874 can cause a denial of service but does not directly allow unauthorized access.

5

Who is impacted by CVE-2014-1874?

Users or processes with CAP_MAC_ADMIN privileges on affected Linux systems are primarily impacted by CVE-2014-1874.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203