CVE-2017-1000253
Exploitation confirmed. First attested on 2024-09-09 by CISA-ADP, CISA KEV, GCVE · kevintel.
- Published2017-10-05
- WeaknessCWE-119
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2017-10-0501:29CVE publishedNVD
- 2024-09-09Listed as exploited by GCVEGCVE
- 2024-09-09Exploitation first reportedCISA KEV
- 2024-09-09Added to the CISA KEV catalogCISA KEV
- 2024-09-1003:55SSVC exploitation set to activeCISA-ADP
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-1000253?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-1000253?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · CISA-ADP| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.0 | = 6.0 | no fix published | NVD · CISA-ADP |
| 6.1 | = 6.1 | no fix published | NVD · CISA-ADP |
| 6.2 | = 6.2 | no fix published | NVD · CISA-ADP |
| 6.3 | = 6.3 | no fix published | NVD · CISA-ADP |
| 6.4 | = 6.4 | no fix published | NVD · CISA-ADP |
| 6.5 | = 6.5 | no fix published | NVD · CISA-ADP |
| 6.6 | = 6.6 | no fix published | NVD · CISA-ADP |
| 6.7 | = 6.7 | no fix published | NVD · CISA-ADP |
| 6.8 | = 6.8 | no fix published | NVD · CISA-ADP |
| 6.9 | = 6.9 | no fix published | NVD · CISA-ADP |
| 7.1406 | = 7.1406 | no fix published | NVD · CISA-ADP |
| 7.1503 | = 7.1503 | no fix published | NVD · CISA-ADP |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.0 | = 6.0 | no fix published | NVD · CISA-ADP |
| 6.1 | = 6.1 | no fix published | NVD |
| 6.2 | = 6.2 | no fix published | NVD |
| 6.3 | = 6.3 | no fix published | NVD |
| 6.4 | = 6.4 | no fix published | NVD |
| 6.5 | = 6.5 | no fix published | NVD |
| 6.6 | = 6.6 | no fix published | NVD |
| 6.7 | = 6.7 | no fix published | NVD |
| 6.8 | = 6.8 | no fix published | NVD |
| 6.9 | = 6.9 | no fix published | NVD |
| 7.0 | = 7.0 | no fix published | NVD |
| 7.1 | = 7.1 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.0 | ≥ 4.0, < 4.0.2 | 4.0.2 | NVD |
| 4.0 | ≥ 1.0, < 4.0.2 | 4.0.2 | CISA-ADP |
| 3.19 | ≥ 3.19, < 3.19.7 | 3.19.7 | NVD · CISA-ADP |
| 3.x | ≥ 3.17, < 3.18.14 | 3.18.14 | NVD · CISA-ADP |
| 3.x | ≥ 3.15, < 3.16.35 | 3.16.35 | NVD · CISA-ADP |
| 3.x | ≥ 3.13, < 3.14.41 | 3.14.41 | NVD · CISA-ADP |
| 3.x | ≥ 3.11, < 3.12.43 | 3.12.43 | NVD · CISA-ADP |
| 3.x | ≥ 3.5, < 3.10.77 | 3.10.77 | NVD · CISA-ADP |
| 3.x | ≥ 3.3, < 3.4.109 | 3.4.109 | NVD · CISA-ADP |
| 3.2 | ≥ 2.6.25, < 3.2.70 | 3.2.70 | NVD · CISA-ADP |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- CISA’s required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.due 2024-09-30
Advisories and patches
- www.qualys.comPatch
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 2 repositories, unverifiedRicterZ/PIE-Stack-Clash-CVE-2017-1000253sxlmnwb/CVE-2017-1000253 PoC-in-GitHub
CISA Known Exploited Vulnerability
- Date Added
- 2024-09-09
- Patch Due Date
- 2024-09-30
- Ransomware Use
- Known
- Required Action
- Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Sources
- CISA KEVKEV entry2024-09-09
- GCVEexploitation2024-09-09
- CISA-ADPSSVC decisionactive2024-09-10
- OpenCVESSVC decisionactive—
- CISA-ADPCVSS 3.17.82024-09-06
- NVDCVSS 3.17.8read 2026-10-23
- NVDCVSS 2.07.2read 2026-10-23
- CISA-ADPweakness (CWE)CWE-1192024-09-06
- NVDweakness (CWE)CWE-119read 2026-10-23
- FIRST EPSSEPSS score10.7 %read 2026-10-23
- PoC-in-GitHubproof of concept2read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2017-10-05
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2017-1000253?
Is CVE-2017-1000253 actively exploited?
What is the CVSS score for CVE-2017-1000253?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.