CVE-2020-1751
An out-of-bounds write vulnerability was found in glibc before 2.31 when handling signal trampolines on PowerPC.
Published Apr 17, 2020 · updated Oct 14, 2026 · gnu glibc
An out-of-bounds write vulnerability was found in glibc before 2.31 when handling signal trampolines on PowerPC. Specifically, the backtrace function did not properly check the array bounds when storing the frame address, resulting in a denial of service or potential code execution. The highest threat from this vulnerability is to system availability.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Apr 17, 2020 · NIST NVD
Detected
An out-of-bounds write vulnerability was found in glibc before 2.31 when handling signal trampolines on PowerPC. Specifically, the backtrace function did not properly check the array bounds when storing the frame address, resulting in a denial of service or potential code execution. The highest threat from this vulnerability is to system availability.
Oct 14, 2026 · NIST NVD
Updated
An out-of-bounds write vulnerability was found in glibc before 2.31 when handling signal trampolines on PowerPC. Specifically, the backtrace function did not properly check the array bounds when storing the frame address, resulting in a denial of service or potential code execution. The highest threat from this vulnerability is to system availability.
Affected
- cpe canonical/ubuntu linux16.04
- cpe canonical/ubuntu linux18.04
- cpe canonical/ubuntu linux19.10
- cpe gnu/glibcversion unspecified
- cpe redhat/enterprise linux8.0
Sources
- CVE.orgVulnerability recordCVE-2020-1751
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2020-1751
30-day exploitation probability 0.5%
first.org - NIST NVDVulnerability recordCVE-2020-1751
An out-of-bounds write vulnerability was found in glibc before 2.31 when handling signal trampolines on PowerPC. Specifically, the backtrace function did not properly check the array bounds when storing the frame address, resulting in a denial of service or potential code executi
nvd.nist.gov