Skip to content
vulnerability

CVE-2017-1000253

7.8
High
KEV · Exploited in wildEPSS 11%Patch available

Linux distributions that have not patched their long-term kernels with https://git.kernel.org/linus/a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (committed on April 14, 2015). This kernel vulnerability was fixed in April 2015 by commit a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (backported to Linux 3.10.77 in May 2015), but it was not recognized as a security threat. With CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE enabled, and a normal top-down address allocation strategy, load_elf_binary() will attempt to map a PIE binary into an address range immediately below mm->mmap_base. Unfortunately, load_elf_ binary() does not take account of the need to allocate sufficient space for the entire binary which means that, while the first PT_LOAD segment is mapped below mm->mmap_base, the subsequent PT_LOAD segment(s) end up being mapped above mm->mmap_base into the are that is supposed to be the "gap" between the stack and the binary.

exploited
Yes, in CISA KEV since 9 Sept 2024fix by 30 Sept 2024 (CISA deadline for US federal agencies)known use in ransomware campaignspublic exploit code
fix
Patch available see the advisory in the references
likelihood
EPSS 10.7%
Published 5 Oct 2017Analysed here 2 Nov 2026CVSS scored by CISA

do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

triage
server-sideruntimeWAF can block: noAV · localCWE-119· Buffer Boundary Error

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectorlocalattack complexitylowprivileges requiredlowuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2017-1000253 being exploited?

Yes. CVE-2017-1000253 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2017-1000253?

CVE-2017-1000253 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2017-1000253?

Yes. A fix has been recorded for CVE-2017-1000253. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2017-1000253 affect?

CVE-2017-1000253 affects centos:centos, redhat:enterprise_linux, linux:linux_kernel. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
centos:centosredhat:enterprise_linuxlinux:linux_kernel

public exploits

Public exploit code: 1 on Exploit-DB · 2 GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 10 Sept 2024 (SSVC 2.0.3).

timeline

  1. 26 Sept 2017First public exploit or proof of concept
  2. 5 Oct 2017Published · 9 days later
  3. 9 Sept 2024Added to CISA KEV (exploited in the wild) · 2,531 days (about 7 years) later
  4. 10 Sept 2024CISA SSVC assessment: exploitation active · 1 day later
  5. 30 Sept 2024CISA remediation due date (US federal agencies) · 20 days later
  6. 21 Oct 2025CVE record last updated · 387 days (about 1 year) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
14 references in the CVE record: 10 advisories, 4 links
Show 6 more

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved