# CVE-2017-1000371: Security feature bypass in n/a

> Attackers can bypass stack guard pages on i386 Linux systems with specific memory limits to achieve privilege escalation or code execution.

- **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:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-1000371, GHSA-wr3q-fcxj-4873, UBUNTU-CVE-2017-1000371

## What is CVE-2017-1000371?

CVE-2017-1000371 is a high-severity vulnerability in Linux kernel, published on 19 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The offset2lib patch as used by the Linux Kernel contains a vulnerability, if RLIMIT_STACK is set to RLIM_INFINITY and 1 Gigabyte of memory is allocated (the maximum under the 1/4 restriction) then the stack will be grown down to 0x80000000, and as the PIE binary is mapped above 0x80000000 the minimum distance between the end of the PIE binary's read-write segment and the start of the stack becomes small enough that the stack guard page can be jumped over by an attacker. This affects Linux Kernel version 4.11.5. This is a different issue than CVE-2017-1000370 and CVE-2017-1000365. This issue appears to be limited to i386 based systems.

## Which versions are affected by CVE-2017-1000371?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2017-1000371?

Apply the vendor's patch.

## Is CVE-2017-1000371 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-1000371 exists.

Public exploit code:

- Linux Kernel - 'offset2lib' Stack Clash (exploitdb)
- Linux Kernel (Debian 9/10 / Ubuntu 14.04.5/16.04.2/17.04 / Fedora 23/24/25) - 'ldso_dynamic Stack Clash' Local Privilege Escalation (exploitdb)
- https://github.com/Trinadh465/linux-4.1.15_CVE-2017-1000371 (github_poc): https://github.com/Trinadh465/linux-4.1.15_CVE-2017-1000371

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000371 and fix it if it is affected.

What it is: CVE-2017-1000371 is a high-severity vulnerability in Linux kernel, published on 19 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-1000371 exists.

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-1000371/ (Markdown: https://insights.sbomify.com/CVE-2017-1000371/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-1000371
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-1000371
- OSV: https://osv.dev/vulnerability/CVE-2017-1000371

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-1000371/
Summaries are generated and may contain mistakes; the official description above is the record.