Threats / Linux / CVE-2014-3153
CVE-2014-3153
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Linux Kernel vulnerability
The futex_requeue function in the Linux kernel fails to validate that requeue operations target distinct futex addresses, allowing local attackers to escalate privileges through improper state manipulation.
Verdict
Today item — known-exploited.
A local privilege escalation vulnerability in Linux kernel futex handling. Attackers with local system access can exploit insufficient address validation in futex_requeue to gain elevated privileges. Active exploitation in the wild confirms practical attack viability.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-05-25).
Probability (EPSS)
EPSS 0.37233 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Linux, Kernel. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-269 Improper Privilege Management — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I gain local system access as an unprivileged user on a vulnerable Linux system.
Business
An attacker establishes a foothold on the system with standard user permissions.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft a futex_requeue call that requeues a futex to itself by bypassing address validation checks.
Business
The vulnerability allows manipulation of kernel synchronization primitives without proper safeguards.
3
Lateral reach — past segmentation narrative 3
Attacker
I trigger a race condition or state corruption in the kernel's futex handling logic through the invalid requeue operation.
Business
Kernel memory integrity is compromised, creating conditions for privilege escalation.
4
Data at risk — exfiltration narrative 4
Attacker
I execute code with root or kernel-level privileges by exploiting the corrupted kernel state.
Business
The attacker gains complete system control, enabling data theft, malware installation, or lateral movement.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05