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.
CVE-2017-1000253
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2024-09-09), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 9.0CRITICALhigh confidence
- EG Risk
- 81EG Risk 81/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%CISA SSVC: Track at low, Attend at medium and Act at high mission impact.Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact. - EPSS PROB
- 11%
- EPSS %ILE
- 95th
- KEV
- ⚠ Exploited
CISA SSVCTrack at low, Attend at medium and Act at high mission impact.
A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 5, 2017
Last Modified
June 17, 2026
Advisory Details (10)
Auto-updated May 19, 2026Affected: Red Hat Enterprise Linux 6.2 Advanced Update Support.
https://access.redhat.com/errata/RHSA-2017:2800Affected: Red Hat Enterprise Linux 6.4 Advanced Update Support.
https://access.redhat.com/errata/RHSA-2017:2799Affected: Red Hat Enterprise Linux 6.5 Advanced Update Support and Red Hat Enterprise Linux 6.5 Telco Extended Update Support.
https://access.redhat.com/errata/RHSA-2017:2798Affected: Red Hat Enterprise Linux 6.6 Advanced Update Support and Red Hat Enterprise Linux 6.6 Telco Extended Update Support.
https://access.redhat.com/errata/RHSA-2017:2797Affected: Red Hat Enterprise Linux 6.7 Extended Update Support.
https://access.redhat.com/errata/RHSA-2017:2796Affected: Red Hat Enterprise Linux 6.
https://access.redhat.com/errata/RHSA-2017:2795Affected: Red Hat Enterprise Linux 7.2 Extended Update Support.
https://access.redhat.com/errata/RHSA-2017:2794Affected: Red Hat Enterprise Linux 7.3 Extended Update Support.
https://access.redhat.com/errata/RHSA-2017:2793Vendor Advisories for CVE-2017-1000253(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(11)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | kernel-0:2.6.18-423.el5 | 2017-09-26 | redhat |
| redhat | kernel-0:2.6.32-431.85.1.el6 | 2017-09-26 | redhat |
| redhat | kernel-0:3.10.0-327.59.3.el7 | 2017-09-26 | redhat |
| redhat | kernel-0:2.6.18-348.34.2.el5 | 2017-09-26 | redhat |
| redhat | kernel-0:3.10.0-514.32.3.el7 | 2017-09-26 | redhat |
| redhat | kernel-0:2.6.32-504.63.3.el6 | 2017-09-26 | redhat |
| redhat | kernel-0:2.6.32-220.76.1.el6 | 2017-09-26 | redhat |
| redhat | kernel-0:2.6.32-696.10.3.el6 | 2017-09-26 | redhat |
| redhat | kernel-0:2.6.32-358.84.1.el6 | 2017-09-26 | redhat |
| redhat | kernel-0:2.6.32-573.48.1.el6 | 2017-09-26 | redhat |
| redhat | kernel-0:3.10.0-693.el7 | 2017-08-01 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(10)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
- Red HatRHSA-2017:2793IMPORTANT2017-09-26
RHSA-2017:2793 — Important
- Red HatRHSA-2017:2794IMPORTANT2017-09-26
RHSA-2017:2794 — Important
- Red HatRHSA-2017:2795IMPORTANT2017-09-26
RHSA-2017:2795 — Important
- Red HatRHSA-2017:2796IMPORTANT2017-09-26
RHSA-2017:2796 — Important
- Red HatRHSA-2017:2797IMPORTANT2017-09-26
RHSA-2017:2797 — Important
- Red HatRHSA-2017:2798IMPORTANT2017-09-26
RHSA-2017:2798 — Important
- Red HatRHSA-2017:2799IMPORTANT2017-09-26
RHSA-2017:2799 — Important
- Red HatRHSA-2017:2800IMPORTANT2017-09-26
RHSA-2017:2800 — Important
- Red HatRHSA-2017:2801IMPORTANT2017-09-26
RHSA-2017:2801 — Important
- Red HatRHSA-2017:2802IMPORTANT2017-09-26
RHSA-2017:2802 — Important
Data Freshness Timeline
(refreshed 102× in last 7d / 448× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 1,873 total refreshes for this CVE.
- 2026-10-06 06:24 UTCVendor advisory
- 2026-10-06 06:24 UTCGHSA enrichment
- 2026-10-06 02:36 UTCVendor advisory
- 2026-10-06 02:36 UTCGHSA enrichment
- 2026-10-05 22:48 UTCVendor advisory
- 2026-10-05 22:48 UTCGHSA enrichment
- 2026-10-05 19:00 UTCEG score recompute
- 2026-10-05 19:00 UTCVendor advisory
- 2026-10-05 19:00 UTCGHSA enrichment
- 2026-10-05 17:38 UTCEPSS rescore
- 2026-10-05 15:12 UTCVendor advisory
- 2026-10-05 15:12 UTCGHSA enrichment
- 2026-10-05 11:22 UTCVendor advisory
- 2026-10-05 11:21 UTCGHSA enrichment
- 2026-10-05 07:34 UTCVendor advisory
- 2026-10-05 07:34 UTCGHSA enrichment
- 2026-10-05 03:46 UTCVendor advisory
- 2026-10-05 03:46 UTCGHSA enrichment
- 2026-10-04 23:59 UTCEG score recompute
- 2026-10-04 23:59 UTCVendor advisory
- 2026-10-04 23:58 UTCGHSA enrichment
- 2026-10-04 23:17 UTCEPSS rescore
- 2026-10-04 20:11 UTCVendor advisory
- 2026-10-04 20:10 UTCGHSA enrichment
- 2026-10-04 16:21 UTCVendor advisory
Show 75 moreShow fewer
- 2026-10-04 16:21 UTCGHSA enrichment
- 2026-10-04 12:33 UTCVendor advisory
- 2026-10-04 12:33 UTCGHSA enrichment
- 2026-10-04 08:46 UTCVendor advisory
- 2026-10-04 08:46 UTCGHSA enrichment
- 2026-10-04 04:58 UTCVendor advisory
- 2026-10-04 04:58 UTCGHSA enrichment
- 2026-10-04 01:11 UTCVendor advisory
- 2026-10-04 01:11 UTCGHSA enrichment
- 2026-10-03 21:24 UTCVendor advisory
- 2026-10-03 21:24 UTCGHSA enrichment
- 2026-10-03 17:36 UTCEG score recompute
- 2026-10-03 17:36 UTCVendor advisory
- 2026-10-03 17:36 UTCGHSA enrichment
- 2026-10-03 14:21 UTCEPSS rescore
- 2026-10-03 14:21 UTCEPSS rescore
- 2026-10-03 13:49 UTCVendor advisory
- 2026-10-03 13:49 UTCGHSA enrichment
- 2026-10-03 09:58 UTCVendor advisory
- 2026-10-03 09:58 UTCGHSA enrichment
- 2026-10-03 06:09 UTCVendor advisory
- 2026-10-03 06:09 UTCGHSA enrichment
- 2026-10-03 02:21 UTCVendor advisory
- 2026-10-03 02:20 UTCGHSA enrichment
- 2026-10-02 22:32 UTCVendor advisory
- 2026-10-02 22:32 UTCGHSA enrichment
- 2026-10-02 18:44 UTCEG score recompute
- 2026-10-02 18:44 UTCVendor advisory
- 2026-10-02 18:44 UTCGHSA enrichment
- 2026-10-02 14:56 UTCVendor advisory
- 2026-10-02 14:56 UTCGHSA enrichment
- 2026-10-02 11:08 UTCVendor advisory
- 2026-10-02 11:08 UTCGHSA enrichment
- 2026-10-02 07:20 UTCVendor advisory
- 2026-10-02 07:20 UTCGHSA enrichment
- 2026-10-02 03:33 UTCVendor advisory
- 2026-10-02 03:33 UTCGHSA enrichment
- 2026-10-01 23:46 UTCVendor advisory
- 2026-10-01 23:45 UTCGHSA enrichment
- 2026-10-01 19:57 UTCEG score recompute
- 2026-10-01 19:57 UTCVendor advisory
- 2026-10-01 19:57 UTCGHSA enrichment
- 2026-10-01 16:09 UTCVendor advisory
- 2026-10-01 16:09 UTCGHSA enrichment
- 2026-10-01 12:22 UTCVendor advisory
- 2026-10-01 12:21 UTCGHSA enrichment
- 2026-10-01 08:33 UTCVendor advisory
- 2026-10-01 08:33 UTCGHSA enrichment
- 2026-10-01 04:45 UTCVendor advisory
- 2026-10-01 04:44 UTCGHSA enrichment
- 2026-10-01 00:53 UTCVendor advisory
- 2026-10-01 00:53 UTCGHSA enrichment
- 2026-09-30 21:05 UTCVendor advisory
- 2026-09-30 21:05 UTCGHSA enrichment
- 2026-09-30 17:17 UTCEG score recompute
- 2026-09-30 17:17 UTCVendor advisory
- 2026-09-30 17:17 UTCGHSA enrichment
- 2026-09-30 14:58 UTCEPSS rescore
- 2026-09-30 13:29 UTCVendor advisory
- 2026-09-30 13:29 UTCGHSA enrichment
- 2026-09-30 09:42 UTCVendor advisory
- 2026-09-30 09:42 UTCGHSA enrichment
- 2026-09-30 05:55 UTCVendor advisory
- 2026-09-30 05:55 UTCGHSA enrichment
- 2026-09-30 02:07 UTCVendor advisory
- 2026-09-30 02:07 UTCGHSA enrichment
- 2026-09-29 22:20 UTCVendor advisory
- 2026-09-29 22:19 UTCGHSA enrichment
- 2026-09-29 18:30 UTCEG score recompute
- 2026-09-29 18:30 UTCVendor advisory
- 2026-09-29 18:30 UTCGHSA enrichment
- 2026-09-29 14:42 UTCVendor advisory
- 2026-09-29 14:42 UTCGHSA enrichment
- 2026-09-29 10:54 UTCVendor advisory
- 2026-09-29 10:54 UTCGHSA enrichment
Publicly available exploits
(3 references)Working exploit code is in the public domain (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCsxlmnwb/CVE-2017-1000253First seen Oct 16, 2022
Linux Kernel 3.10.0-514.21.2.el7.x86_64 / 3.10.0-514.26.1.el7.x86_64 (CentOS 7) - SUID Position Independent Executable 'PIE' Local Privilege Escalation
Open source ↗ - GitHub PoCRicterZ/PIE-Stack-Clash-CVE-2017-1000253First seen Jun 18, 2018
Demo-ing CVE-2017-1000253 in a container
Open source ↗ - Exploit-DBEDB-42887First seen Sep 26, 2017
Linux Kernel 3.10.0-514.21.2.el7.x86_64 / 3.10.0-514.26.1.el7.x86_64 (CentOS 7) - SUID Position Independent Executable 'PIE' Local Privilege Escalation
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat:RHSA-2017:1842
Frequently asked(6)
What is CVE-2017-1000253?
When was CVE-2017-1000253 disclosed?
Is CVE-2017-1000253 actively exploited?
What is the CVSS score of CVE-2017-1000253?
Which products are affected by CVE-2017-1000253?
How do I remediate CVE-2017-1000253?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-1000253
Is Your Infrastructure Affected by CVE-2017-1000253?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.