LiveActive security incident?Get immediate response
CVE Record

CVE-2017-1000253: Linux distributions that have not patched their long-term kernels with https://git.kernel.org/linus/a87938b...

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.

HighCVSS 7.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel local privilege escalation issue. A user who already has access to a vulnerable machine may be able to abuse incorrect PIE binary memory mapping to gain powerful system privileges. It is not a remote internet entry point, but CISA KEV listing means it has known exploitation significance.

Executive priority

Prioritize remediation for legacy Linux systems with local users, shared hosting, developer access, or internet-facing services that could first be compromised another way. Treat as high priority because KEV confirms known exploitation relevance, but scope it through kernel inventory rather than assuming every Linux host is affected.

Technical view

The flaw is in load_elf_binary() handling of PIE ELF mappings when CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE and top-down allocation are used. Some long-term kernels missed the 2015 upstream fix or backport, allowing later PT_LOAD segments to map into the stack gap area. CVSS is 7.8, local, low complexity, low privilege required.

Likely exposure

Exposure is most likely on Linux distributions or appliances running older long-term kernels that did not include commit a87938b2e246b81b4fb713edb371a9fa3c5c3c86 or the Linux 3.10.77 backport. The bundle does not provide a complete affected product matrix.

Exploitation context

CISA lists CVE-2017-1000253 in KEV, supporting known exploitation. The source bundle does not provide current campaign details. Exploitation requires local access with low privileges, making shared servers, legacy workloads, and multi-user Linux environments higher concern.

Researcher notes

The key research question is whether a distribution backported a87938b2e246b81b4fb713edb371a9fa3c5c3c86 into its maintained kernel. The bundle indicates the bug was fixed upstream in April 2015 and backported to Linux 3.10.77 in May 2015, but not recognized as security-impacting until later.

Mitigation direction

  • Apply the vendor kernel update or advisory package for affected Linux distributions.
  • Confirm the running kernel includes the 2015 upstream fix or relevant backport.
  • Reboot into the patched kernel; installed packages alone may not remove exposure.
  • Retire unsupported kernels that no longer receive security backports.
  • Follow vendor guidance where product-specific applicability is unclear.

Validation and detection

  • Inventory Linux kernel versions across servers, containers hosts, and appliances.
  • Compare kernels against vendor advisories and the upstream fixed commit/backport.
  • Verify the patched kernel is the active booted kernel after reboot.
  • Check bootloader defaults for older vulnerable kernels.
  • Review local user access on legacy multi-user systems.
Prepared
Confidence
high
Sources
8

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.

cwe · low confidence lookup

CWE-119: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-1000253 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
High
CVSS
7.8 (3.1)
Known Exploited
Yes
Published

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

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.

1CVSS vectors
0Timeline events
0ADP providers
13Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2017-1000253Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-119 · source CWE mapping

Improper Restriction of Operations within the Bounds of a Memory Buffer

Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.