CVE-2017-1000253

See a problem?
Please try reporting it to the source first.
Source
https://nvd.nist.gov/vuln/detail/CVE-2017-1000253
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2017-1000253.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2017-1000253
Related
Published
2017-10-05T01:29:04Z
Modified
2024-09-18T01:00:22Z
Severity
  • 7.8 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
Summary
[none]
Details

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 CONFIGARCHBINFMTELFRANDOMIZEPIE enabled, and a normal top-down address allocation strategy, loadelfbinary() will attempt to map a PIE binary into an address range immediately below mm->mmapbase. Unfortunately, loadelf binary() does not take account of the need to allocate sufficient space for the entire binary which means that, while the first PTLOAD segment is mapped below mm->mmapbase, the subsequent PTLOAD segment(s) end up being mapped above mm->mmapbase into the are that is supposed to be the "gap" between the stack and the binary.

References

Affected packages

Debian:11 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
4.0.2-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:12 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
4.0.2-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
4.0.2-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}