Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 7.8 CISA Known Exploited Vulnerability

CVE-2014-3153

Linux Kernel Privilege Escalation Vulnerability

Linux Kernel

The futex_requeue function in kernel/futex.c in the Linux kernel through 3.14.5 does not ensure that calls have two different futex addresses, which allows local users to gain privileges via a crafted FUTEX_REQUEUE command that facilitates unsafe waiter modification.

CVSS
7.8
HIGH
EPSS
37.2%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
7 Jun 2014
NVD

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 25 May 2022. US federal agencies were required to remediate it by 15 June 2022.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 37.2%, which is higher than 98.5% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

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

Frequently asked questions

Is CVE-2014-3153 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2014-3153.

What does CVE-2014-3153 affect?

CVE-2014-3153 affects Linux Kernel. The futex_requeue function in kernel/futex.c in the Linux kernel through 3.14.5 does not ensure that calls have two different futex addresses, which allows local users to gain privileges via a crafted FUTEX_REQUEUE command that facilitates unsafe waiter modification.

How severe is CVE-2014-3153?

CVE-2014-3153 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 37.2%, higher than 98.5% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 15 June 2022.

How should organisations respond to CVE-2014-3153?

Apply the vendor patch for Linux Kernel as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.