Answer in brief
CVE-2017-1000253 records a High severity vulnerability in CVE Program Container. The current sources mark it as known exploited. The current feed maps centos/centos (generic), centos/centos (generic), centos/centos (generic), centos/centos (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2017-1000253 records a High severity vulnerability in CVE Program Container. The current sources mark it as known exploited. The current feed maps centos/centos (generic), centos/centos (generic), centos/centos (generic), centos/centos (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. Known-exploitation status makes exposure review time-sensitive. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps centos/centos (generic), centos/centos (generic), centos/centos (generic), centos/centos (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| centos/centosgeneric | 6.0 | Not reported |
| centos/centosgeneric | 6.1 | Not reported |
| centos/centosgeneric | 6.2 | Not reported |
| centos/centosgeneric | 6.3 | Not reported |
| centos/centosgeneric | 6.4 | Not reported |
| centos/centosgeneric | 6.5 | Not reported |
| centos/centosgeneric | 6.6 | Not reported |
| centos/centosgeneric | 6.7 | Not reported |
| centos/centosgeneric | 6.8 | Not reported |
| centos/centosgeneric | 6.9 | Not reported |
| centos/centosgeneric | 7.1406 | Not reported |
| centos/centosgeneric | 7.1503 | Not reported |
| centos/centosgeneric | 7.1511 | Not reported |
| centos/centosgeneric | 7.1611 | Not reported |
| redhat/enterprise_linuxgeneric | 6.0 || 6.1 || 6.2 || 6.3 || 6.4 || 6.5 || 6.6 || 6.7 || 6.8 || 6.9 || 7.0 || 7.1 || 7.2 || 7.3 | Not reported |
| linux/linux_kernelgeneric | >=2.6.25 <3.2.70 || >=3.3 <3.4.109 || >=3.5 <3.10.77 || >=3.11 <3.12.43 || >=3.13 <3.14.41 || >=3.15 <3.16.35 || >=3.17 <3.18.14 || >=3.19 <3.19.7 || >=1.0 <4.0.2 | 3.2.70, 3.4.109, 3.10.77, 3.12.43, 3.14.41, 3.16.35, 3.18.14, 3.19.7, 4.0.2 |
| n/a/n/ageneric | n/a | Not reported |
Published upstream
Oct 4, 2017
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2025
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
May 24, 2026
Added to CISA KEV
Sep 9, 2024
Evidence: source:kev:kev:kev:recordLinux 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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. Known-exploitation status makes exposure review time-sensitive. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps centos/centos (generic), centos/centos (generic), centos/centos (generic), centos/centos (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| centos/centosgeneric | 6.0 | Not reported |
| centos/centosgeneric | 6.1 | Not reported |
| centos/centosgeneric | 6.2 | Not reported |
| centos/centosgeneric | 6.3 | Not reported |
| centos/centosgeneric | 6.4 | Not reported |
| centos/centosgeneric | 6.5 | Not reported |
| centos/centosgeneric | 6.6 | Not reported |
| centos/centosgeneric | 6.7 | Not reported |
| centos/centosgeneric | 6.8 | Not reported |
| centos/centosgeneric | 6.9 | Not reported |
| centos/centosgeneric | 7.1406 | Not reported |
| centos/centosgeneric | 7.1503 | Not reported |
| centos/centosgeneric | 7.1511 | Not reported |
| centos/centosgeneric | 7.1611 | Not reported |
| redhat/enterprise_linuxgeneric | 6.0 || 6.1 || 6.2 || 6.3 || 6.4 || 6.5 || 6.6 || 6.7 || 6.8 || 6.9 || 7.0 || 7.1 || 7.2 || 7.3 | Not reported |
| linux/linux_kernelgeneric | >=2.6.25 <3.2.70 || >=3.3 <3.4.109 || >=3.5 <3.10.77 || >=3.11 <3.12.43 || >=3.13 <3.14.41 || >=3.15 <3.16.35 || >=3.17 <3.18.14 || >=3.19 <3.19.7 || >=1.0 <4.0.2 | 3.2.70, 3.4.109, 3.10.77, 3.12.43, 3.14.41, 3.16.35, 3.18.14, 3.19.7, 4.0.2 |
| n/a/n/ageneric | n/a | Not reported |
Published upstream
Oct 4, 2017
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2025
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
May 24, 2026
Added to CISA KEV
Sep 9, 2024
Evidence: source:kev:kev:kev:recordLinux 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.
Quoted source text, attributed separately from HOL analysis.