Linux Kernel PIE Stack Buffer Corruption Vulnerability
Linux · Kernel
The Linux kernel's ELF loader (load_elf_binary() in the binfmt code) fails to reserve enough address space for all PT_LOAD segments of a PIE binary when CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE is enabled, so later segments can be mapped into the gap between the stack and the binary, causing memory buffer corruption. An attacker with a local, low-privilege account can trigger it by running a crafted PIE binary, with no user interaction or special configuration beyond that kernel option and default top-down address allocation.
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.
- Exploited
- Yes, in CISA KEV
- Reports
- 0
- Tactics
- 2/15
How an attack unfolds
Based on MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. mappings. Select a step to see the evidence.Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 4 years after disclosure. Public exploit code (Exploit-DB) was available 9 days before disclosure.
- Public exploit codeExploit-DB9 days before
- Disclosedday 0
- First seen exploitedVulnCheck KEV evidence+4 yrs
- Added to CISA KEVknown ransomware use; EU database agrees+7 yrs
CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
1 TechniqueOne specific attacker behaviour in MITRE ATT&CK, such as T1190 “Exploit Public-Facing Application”. IDs with a dot, like T1059.004, are sub-techniques., grouped by TacticThe attacker’s goal at a stage of an attack in MITRE ATT&CK, such as Initial Access or Persistence. Each technique belongs to one or more tactics. in kill-chain order, 1 cited passage 1Privilege EscalationTA0004
memory layout corruption enables code injection into processes
subsequent PT_LOAD segment(s) end up being mapped above mm->mmap_base
Detection
0 rules for this CVE · 37 general rules for its techniquesRules for this CVE
0Sigma ruleAn open, vendor-neutral detection rule for log data. Security teams convert Sigma rules into searches for their own SIEM. that reference CVE-2017-1000253 directly.CVE-specific rules are not available in this build. Search SigmaHQ ↗
General rules for this CVE’s techniques
These detect the technique in general, not this specific vulnerability.
Process InjectionT105537 general rules
- Antivirus PrinterNightmare CVE-2021-34527 Exploit Detectioncriticalstable
- Potential Dridex Activitycriticalstable
- CobaltStrike Named Pipecriticaltest
- CobaltStrike Named Pipe Pattern Regexcriticaltest
- HackTool - DInjector PowerShell Cradle Executioncriticaltest
- Malicious Named Pipe Createdcriticaltest
- RedSun - Named Pipe Createdcriticalexperimental
- RedSun - TieringEngineService.exe Detected as EICAR Test Filecriticalexperimental
Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.
What security researchers reported
Not named in any threat report yetAlso mentioned in 50 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Actively_Exploited_Kev | Oct 29, 202628 Oct 2026
- Actively_Exploited_Kev | Oct 28, 202627 Oct 2026
- Actively_Exploited_Kev | Oct 27, 202626 Oct 2026
- Actively_Exploited_Kev | Oct 24, 202623 Oct 2026
- Actively_Exploited_Kev | Oct 23, 202622 Oct 2026
- Actively_Exploited_Kev | Oct 22, 202621 Oct 2026
- 44 more on OTX