# CVE-2017-1000253: Linux Kernel PIE Stack Buffer Corruption Vulnerability > A flaw in Linux kernel ELF loading allows attackers to corrupt memory and potentially escalate privileges or execute code when PIE randomization is enabled. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Yes, since 9 Sep 2024 (CISA KEV), used in ransomware - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 4 Oct 2017 - **Updated:** 21 Oct 2025 - **Also known as:** DEBIAN-CVE-2017-1000253, GHSA-rm92-8pw8-34fm, RHSA-2017:2793, RHSA-2017:2794, RHSA-2017:2795, RHSA-2017:2796, RHSA-2017:2797, RHSA-2017:2798, RHSA-2017:2799, RHSA-2017:2800, RHSA-2017:2801, RHSA-2017:2802, SUSE-SU-2017:2723-1, SUSE-SU-2017:2725-1, UBUNTU-CVE-2017-1000253 ## What is CVE-2017-1000253? CVE-2017-1000253 is a high-severity memory corruption vulnerability in Linux kernel, published on 4 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim. ### Official 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. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2017-1000253? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kernel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debug` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debug-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-doc` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-firmware` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-headers` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `perf` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `perf-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `python-perf` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `python-perf-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.10.3.el6 | | `kernel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debug` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debug-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-doc` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-firmware` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-headers` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `perf` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `perf-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `python-perf` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `python-perf-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.10.3.el6 | | `kernel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-bootwrapper` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debug` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debug-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.10.3.el6 | | `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.10.3.el6 | Products: Centos Centos, Linux kernel, Redhat Enterprise Linux. ## How do I fix CVE-2017-1000253? Apply the vendor's patch. US federal agencies must fix it by 30 Sep 2024. ## Is CVE-2017-1000253 being exploited? Yes. Attackers have exploited CVE-2017-1000253 in the wild since at least 9 Sep 2024, including in ransomware campaigns. Public exploit code: - Demo-ing CVE-2017-1000253 in a container (github_poc): https://github.com/RicterZ/PIE-Stack-Clash-CVE-2017-1000253 - 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 (github_poc): https://github.com/sxlmnwb/CVE-2017-1000253 - 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 (exploitdb) ## Other vulnerabilities in Linux kernel - [CVE-2011-4144](https://insights.sbomify.com/CVE-2011-4144/): Privilege escalation in n/a (medium 6.8) - [CVE-2007-6283](https://insights.sbomify.com/CVE-2007-6283/): Information disclosure in n/a (medium 4.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-1000253 and fix it if it is affected. What it is: CVE-2017-1000253 is a high-severity memory corruption vulnerability in Linux kernel, published on 4 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: Yes. Attackers have exploited CVE-2017-1000253 in the wild since at least 9 Sep 2024, including in ransomware campaigns. Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-1000253/ (Markdown: https://insights.sbomify.com/CVE-2017-1000253/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-1000253 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-1000253 - OSV: https://osv.dev/vulnerability/CVE-2017-1000253 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-1000253/ Summaries are generated and may contain mistakes; the official description above is the record.