Bug 1810719 (CVE-2020-1751) - CVE-2020-1751 glibc: array overflow in backtrace functions for powerpc
Summary: CVE-2020-1751 glibc: array overflow in backtrace functions for powerpc
Alias: CVE-2020-1751
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1811589 1813399
Blocks: 1810721
TreeView+ depends on / blocked
Reported: 2020-03-05 19:08 UTC by Guilherme de Almeida Suckevicz
Modified: 2023-12-15 17:28 UTC (History)
16 users (show)

Fixed In Version: glibc 2.31
Doc Type: If docs needed, set a value
Doc Text:
An out-of-bounds write vulnerability was found in glibc when handling signal trampolines on PowerPC. 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.
Clone Of:
Last Closed: 2020-11-04 02:24:41 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4444 0 None None None 2020-11-04 01:00:39 UTC

Description Guilherme de Almeida Suckevicz 2020-03-05 19:08:02 UTC
When unwinding through a signal frame the backtrace function on PowerPC didn't check array bounds when storing the frame address.


Upstream commit:

Comment 1 Michael Kaplan 2020-03-09 10:01:47 UTC
Created glibc tracking bugs for this issue:

Affects: fedora-all [bug 1811589]

Comment 5 Mauro Matteo Cascella 2020-04-17 14:09:50 UTC

This flaw did not affect the versions of `glibc` as shipped with Red Hat Enterprise Linux 5, 6, and 7, as they did not include the vulnerable code, which was introduced in a later version of the package.

Comment 6 errata-xmlrpc 2020-11-04 01:00:53 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2020:4444 https://access.redhat.com/errata/RHSA-2020:4444

Comment 7 Product Security DevOps Team 2020-11-04 02:24:41 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


Note You need to log in before you can comment on or make changes to this bug.