Look up another CVE · open CVE-2017-1000253 in the interactive tracker
CVE-2017-1000253
Linux distributions that have not patched their long-term kernels with https://git.kernel.org/linus/a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (committed on April…
The kernel CNA record carries no publication date. Subsystem unknown. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2017-1000253 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixed | 4.0.2-1 | Update the kernel and reboot. Fixed in 4.0.2-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 4.0.2-1 | Update the kernel and reboot. Fixed in 4.0.2-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 4.0.2-1 | Update the kernel and reboot. Fixed in 4.0.2-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 4.0.2-1 | Update the kernel and reboot. Fixed in 4.0.2-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
Show whether Debian builds this, per release
Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.
- bookworm, trixie, forky, sid?
- ?
- not established - no Makefile entry for the affected file
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.
Known to be exploited in the wild
- Added to KEV
- 2024-09-09
- Federal due date
- 2024-09-30
- Ransomware use
- known
- Required action
- Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Signals
- Published
- unknown
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 10.70%, higher than 95.8% of all CVEssource
- CISA KEV
- listed, known ransomware usethe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- unknown
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2017-1000253, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.