Threats / Linux / CVE-2017-1000253
CVE-2017-1000253
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Linux Kernel vulnerability
Linux kernel stack buffer corruption in load_elf_binary() allows local privilege escalation via PIE bypass.
Verdict
Today item, not a backlog item.
A local attacker can exploit stack buffer corruption in the ELF binary loader to escalate privileges on affected Linux systems. Active exploitation and ransomware deployment have been observed in the wild.
CISA KEV Yes · 2024-09-094Ransomware use Flagged4EPSS 0.10695 (verify live)5Exploit Public PoC6CVSS 7.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
3 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 2024-09-09), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.10695 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) · Affected: Linux, Kernel. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-119 Memory Buffer Bounds Error — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 2532 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
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
Gain local system access through initial compromise or valid credentials.
Business
Attacker establishes foothold on target infrastructure.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Craft malicious ELF binary that triggers stack buffer overflow in load_elf_binary().
Business
Attacker bypasses memory protections designed to prevent code execution.
3
Lateral reach — past segmentation narrative 3
Attacker
Execute crafted binary to corrupt stack and redirect control flow to arbitrary code.
Business
Attacker achieves code execution with elevated privileges.
4
Data at risk — exfiltration narrative 4
Attacker
Escalate to root or system-level privileges on the compromised host.
Business
Attacker gains complete system control and persistence capability.
5
Lights out — disruption & extortion narrative 5
Attacker
Deploy ransomware or lateral movement tools across the network.
Business
Organization faces data encryption, operational disruption, and potential financial extortion.
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