CVE-2017-1000371: n/a vulnerability

CVE-2017-1000371: The offset2lib patch as used by the Linux Kernel contains a vulnerability, if RLIMIT_STACK is set to RLIM_I...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 5, 2024, 22:00 UTC (UTC+00:00)

Security readout for executives and security teams

This is a Linux kernel stack-guard weakness tied to the 2017 Stack Clash class. It appears limited to i386 systems and Linux kernel 4.11.5 according to the CVE text. The main business risk is legacy 32-bit Linux hosts where a local attacker could bypass memory safety protections. Exposure appears narrow: i386-based Linux systems, specifically kernel 4.11.5 per the CVE record. Modern 64-bit fleets are less likely affected, but legacy appliances, old VMs, and unsupported distributions should be checked. Prioritize targeted verification over broad emergency action. This is old and apparently architecture-limited, but public exploit references make unpatched legacy i386 systems worth finding and fixing quickly. Mitigation focus: Inventory i386 Linux systems and kernel versions.; Check Debian, Red Hat, and distribution advisories for fixed kernel packages.; Prioritize upgrades for Linux 4.11.5 or vendor-confirmed affected kernels..

Prepared: Jun 13, 2026, 04:43 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-1000371 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jun 19, 2017, 16:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txtCVE reference · x_refsource_MISC
42276CVE reference · exploit, x_refsource_EXPLOIT-DB
42273CVE reference · exploit, x_refsource_EXPLOIT-DB
https://access.redhat.com/security/cve/CVE-2017-1000371CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.