CVE-2017-1000253

Advisory lineage Upstream: 0 Downstream: 17
Analyzed
Published: 04 Oct 2017, 01:00
Last modified:21 Oct 2025, 23:55

Vulnerability Summary

Overall Risk (default)
high
53/100
CVSS Score
7.8 HIGH
v3.1 (cve.org)
EPSS Score
57.27% CRITICAL
57% probability +0.06%
KEV
Listed
CISA
1 listing
Ransomware
Known Use
Public exploits
1 found
Dark Web
Not detected

Timeline

04 Oct 2017, 01:00
Published
Vulnerability first disclosed
09 Sept 2024, 00:00
Added to CISA KEV
Linux Kernel PIE Stack Buffer Corruption Vulnerability
30 Sept 2024, 00:00
CISA Remediation Due
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
21 Oct 2025, 23:55
Last Modified
Vulnerability information updated

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.

CVSS Metrics

  • v3.1•HIGH•Score: 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
  • v2.0•HIGH•Score: 7.2AV:L/AC:L/Au:N/C:C/I:C/A:C

EPSS Trends

Current EPSS score: 57.27%• Percentile: 98%

Techniques & Countermeasures

  • CWE-119•Improper Restriction of Operations within the Bounds of a Memory Buffer

    The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

Affected Systems

  • centos•centos

    6.0 | 6.1 | 6.2 | 6.3 | 6.4 | 6.5 | 6.6 | 6.7 | 6.8 | 6.9 | 7.1406 | 7.1503 | 7.1511 | 7.1611

  • linux•linux_kernel

    ≥ 2.6.25, < 3.2.70 | ≥ 3.3, < 3.4.109 | ≥ 3.5, < 3.10.77 | ≥ 3.11, < 3.12.43 | ≥ 3.13, < 3.14.41 | ≥ 3.15, < 3.16.35 | ≥ 3.17, < 3.18.14 | ≥ 3.19, < 3.19.7 | ≥ 4.0, < 4.0.2

  • redhat•enterprise_linux

    6.0 | 6.1 | 6.2 | 6.3 | 6.4 | 6.5 | 6.6 | 6.7 | 6.8 | 6.9 | 7.0 | 7.1 | 7.2 | 7.3

References (14)