Bug 1302673 - CVE-2016-2070 kernel: potential division by zero in TCP code [fedora-all]
CVE-2016-2070 kernel: potential division by zero in TCP code [fedora-all]
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
22
All Linux
medium Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
: Security, SecurityTracking
Depends On:
Blocks: CVE-2016-2070
  Show dependency treegraph
 
Reported: 2016-01-28 06:22 EST by Vladis Dronov
Modified: 2016-02-09 10:08 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Release Note
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-02-09 10:08:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Vladis Dronov 2016-01-28 06:22:52 EST
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.

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:
http://fedoraproject.org/wiki/Security/TrackingBugs

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.

Reproducers, if any, will remain confidential and never be made public, unless done so by the security team.

[bug automatically created by: add-tracking-bugs]
Comment 1 Vladis Dronov 2016-01-28 06:23:00 EST
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)
type=security

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1302219,1302673

# Description of your update
notes=Security fix for CVE-2016-2070

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi update submission link(s) instead:

https://bodhi.fedoraproject.org/updates/new?type_=security&bugs=1302219,1302673
Comment 2 Vladis Dronov 2016-01-28 06:25:12 EST
commit 3759824d introduced the flaw in v4.3-rc1.
an upstream fix is in since v4.4:

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8b8a321ff72c785ed5e8b4cf6eda20b35d427390
Comment 3 Josh Boyer 2016-01-28 08:25:10 EST
(In reply to Vladis Dronov from comment #2)
> commit 3759824d introduced the flaw in v4.3-rc1.
> an upstream fix is in since v4.4:
> 
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/
> ?id=8b8a321ff72c785ed5e8b4cf6eda20b35d427390

That is queued for the 4.3.5 stable release, which is scheduled to come out tomorrow.  We likely are not going to be doing a build for F22 or F23 before then so we will pick it up with 4.3.5.

Rawhide already has the fix.
Comment 4 Josh Boyer 2016-02-09 10:08:09 EST
4.3.5 went stable yesterday.  This is fixed.

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