Skip to content
Noroxi
CVE-2017-1000371· NVD / CVE Program· CNA mitre

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

Noroxi assessment

Priority: Monitor (action score 32/100)

  • Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.5% (FIRST EPSS); higher than 85.1% of all records.
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: linux (Debian:12) 4.11.11-1; linux (Debian:8) 3.16.43-2+deb8u5; linux (Debian:9) 4.9.30-2+deb9u5.

Low priority for now. Upgrade to linux (Debian:12) 4.11.11-1; linux (Debian:8) 3.16.43-2+deb8u5; linux (Debian:9) 4.9.30-2+deb9u5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—Proof of concept Fix available
Published
Jun 19, 2017
Updated
Jun 16, 2026
EPSS
2.5% · 85th percentile
CWE
—

Report tools

JSON

Action score

32

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.5%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2017-1000371

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.1 and later · before 4.1.43
  • linux linux kernel4.2 and later · before 4.4.78
  • linux linux kernel4.5 and later · before 4.9.39
  • linux linux kernel4.10 and later · before 4.11.12
  • linux linux kernel4.12 and later · before 4.12.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 4.11.11-14.11.11-1
Debian:8linuxbefore 3.16.43-2+deb8u53.16.43-2+deb8u5
Debian:9linuxbefore 4.9.30-2+deb9u54.9.30-2+deb9u5
Red Hat:enterprise_linux:6::clientkernelbefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::clientkernel-abi-whitelistsbefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::clientkernel-debugbefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::clientkernel-debug-debuginfobefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::clientkernel-debug-develbefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::clientkernel-debuginfobefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::clientkernel-debuginfo-common-i686before 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::clientkernel-debuginfo-common-x86_64before 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::clientkernel-develbefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::clientkernel-docbefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::clientkernel-firmwarebefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::clientperfbefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::clientperf-debuginfobefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::clientpython-perfbefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::clientpython-perf-debuginfobefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::serverkernel-bootwrapperbefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::serverkernel-debuginfo-common-ppc64before 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::serverkernel-debuginfo-common-s390xbefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::serverkernel-kdumpbefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::serverkernel-kdump-debuginfobefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6
Red Hat:enterprise_linux:6::serverkernel-kdump-develbefore 0:2.6.32-754.29.1.el60:2.6.32-754.29.1.el6

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2017-1000365Jun 19, 2017 · The Linux Kernel imposes a size restriction on the arguments and environmental strings passed through RLIMIT_STACK/RLIM_INFINITY (1/4 of the
    31Monitor
  • ← EarlierCVE-2017-1000370Jun 19, 2017 · The offset2lib patch as used in the Linux Kernel contains a vulnerability that allows a PIE binary to be execve()'ed with 1GB of arguments o
    32Monitor
  • Later →CVE-2017-1000377Jun 19, 2017 · An issue was discovered in the size of the default stack guard page on PAX Linux (originally from GRSecurity but shipped by other Linux vend
    23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:linux4.11.11-1 · Debian:12Package registry (OSV)
red hat:kernel0:2.6.32-754.29.1.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:kernel-abi-whitelists0:2.6.32-754.29.1.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:kernel-debug0:2.6.32-754.29.1.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:kernel-debug-debuginfo0:2.6.32-754.29.1.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:kernel-debug-devel0:2.6.32-754.29.1.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:kernel-debuginfo0:2.6.32-754.29.1.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:kernel-debuginfo-common-i6860:2.6.32-754.29.1.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:kernel-debuginfo-common-x86_640:2.6.32-754.29.1.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:kernel-devel0:2.6.32-754.29.1.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:kernel-doc0:2.6.32-754.29.1.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:kernel-firmware0:2.6.32-754.29.1.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:perf0:2.6.32-754.29.1.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Exploit-DB entry ×2
  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entrylocal2017-06-28
Exploit-DB entrylocal2017-06-28
Proof-of-concept repository on GitHubstars:02023-02-02

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+8 d
  3. TodayOct 25, 2026+3415 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records