Bug 1820332 - CVE-2020-6096 glibc: signed comparison vulnerability in the ARMv7 memcpy function [fedora-all]
Summary: CVE-2020-6096 glibc: signed comparison vulnerability in the ARMv7 memcpy func...
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 31
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Florian Weimer
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: CVE-2020-6096
TreeView+ depends on / blocked
Reported: 2020-04-02 18:38 UTC by Guilherme de Almeida Suckevicz
Modified: 2020-05-19 13:28 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed:
Type: ---

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Sourceware 25620 P2 NEW Signed comparison vulnerability in the ARMv7 memcpy() (CVE-2020-6096) 2020-05-27 13:49:36 UTC

Description Guilherme de Almeida Suckevicz 2020-04-02 18:38:01 UTC
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

Comment 1 Guilherme de Almeida Suckevicz 2020-04-02 18:38:04 UTC
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.


# bugfix, security, enhancement, newpackage (required)

# low, medium, high, urgent (required)

# testing, stable

# Bug numbers: 1234,9876

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# Enable request automation based on the stable/unstable karma thresholds

# Automatically close bugs when this marked as stable

# Suggest that users restart after update


Additionally, you may opt to use the bodhi web interface to submit updates:


Comment 2 Florian Weimer 2020-04-07 13:14:26 UTC
This is blocked on acceptance of a fix upstream.

Comment 3 Carlos O'Donell 2020-04-21 14:36:47 UTC
This is still waiting on upstream bug fix.

However, we now have a proposed fix that is being discussed upstream:

Comment 4 Carlos O'Donell 2020-04-21 14:41:37 UTC
v2 for review:

Comment 8 Carlos O'Donell 2020-05-12 13:11:56 UTC
Updated patch from Huawei has been posted:


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