Bug 1906782 (CVE-2020-16590) - CVE-2020-16590 binutils: double free vulnerability in process_symbol_table could result in DoS
Summary: CVE-2020-16590 binutils: double free vulnerability in process_symbol_table co...
Alias: CVE-2020-16590
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1906783 1906784
Blocks: 1906786
TreeView+ depends on / blocked
Reported: 2020-12-11 11:57 UTC by Michael Kaplan
Modified: 2021-02-16 18:44 UTC (History)
23 users (show)

Fixed In Version: binutils 2.35
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-12-23 00:27:55 UTC

Attachments (Terms of Use)

Description Michael Kaplan 2020-12-11 11:57:23 UTC
A double free vulnerability exists in the Binary File Descriptor (BFD) (aka libbrd) in GNU Binutils 2.34 in the process_symbol_table, as demonstrated in readelf, via a crafted file.

External References:


Comment 1 Michael Kaplan 2020-12-11 11:58:23 UTC
Created binutils tracking bugs for this issue:

Affects: fedora-32 [bug 1906783]

Created mingw-binutils tracking bugs for this issue:

Affects: fedora-all [bug 1906784]

Comment 3 Todd Cullum 2020-12-21 23:49:10 UTC
Flaw summary:

This flaw is a simple typo where `chains` is free()'d but `bucket` is accidentally set to NULL instead of chains. Since chains is not set to NULL, this can result in a double-free. It doesn't exist in the code we ship in 2.30 or 2.35 and thus is not affected.

Comment 4 Todd Cullum 2020-12-22 20:09:16 UTC

binutils as shipped in Red Hat Developer Toolsets 9 and 10, Red Hat Enterprise Linux 8 BaseOS and GCC Toolsets 9 and 10, are all not affected by this flaw as it was introduced in a newer version of binutils code than shipped for BaseOS and the 9 toolsets, but already patched in the versions shipped with 10 toolsets.

Comment 5 Product Security DevOps Team 2020-12-23 00:27:55 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.