CVE-2017-1000253

HIGH
7.8
CVSS Score
Published: October 4, 2017 at 01:00 AM UTC
Updated: June 17, 2026 at 12:58 AM UTC
3 products affected across 3 vendorsLinux KernelEnterprise LinuxCentos

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploitation
CISA KEV
Exploit prediction
EPSS 11%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score10.7%

EPSS (Exploit Prediction Scoring System) estimates a 10.7% chance this CVE is exploited in the wild within the next 30 days — higher than 96% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

Linux kernel contains a position-independent executable (PIE) stack buffer corruption vulnerability in load_elf_ binary() that allows a local attacker to escalate privileges.

Required Action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Ransomware Use
Known
Added to KEV
Sep 9, 2024
Remediation Due
Sep 30, 2024
756 days overdue

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.0 ≤ v < 4.0.22.6.25 ≤ v < 3.2.703.11 ≤ v < 3.12.433.13 ≤ v < 3.14.413.15 ≤ v < 3.16.353.17 ≤ v < 3.18.143.19 ≤ v < 3.19.73.3 ≤ v < 3.4.1093.5 ≤ v < 3.10.774.0 ≤ v < 4.0.21.02.6.253.113.133.153.173.193.33.5
Affected range stops below 3.10.77, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.12.43, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.14.41, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.16.35, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.18.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.19.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.70, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.109, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.2, so it looks safe — our inference, not a vendor statement

References (14)

VDB Entryx_refsource_BIDThird Party Advisory
http://www.securityfocus.com/bid/101010
VDB Entryx_refsource_SECTRACKThird Party Advisory
http://www.securitytracker.com/id/1039434
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2017:2793
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2017:2794
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2017:2795
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2017:2796
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2017:2797
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2017:2798

SSVC — Action Prioritization

SSVCActiveNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-119

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card