Bug 871923 - CVE-2012-4565 kernel: net: divide by zero in tcp algorithm illinois [fedora-all]
Summary: CVE-2012-4565 kernel: net: divide by zero in tcp algorithm illinois [fedora-all]
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Whiteboard: AcceptedNTH
: 866523 (view as bug list)
Depends On:
Blocks: F18Beta-accepted, F18BetaFreezeExcept CVE-2012-4565
TreeView+ depends on / blocked
Reported: 2012-10-31 17:51 UTC by Petr Matousek
Modified: 2013-01-02 17:12 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Release Note
Doc Text:
Clone Of:
Last Closed: 2012-11-08 09:43:32 UTC
Type: ---

Attachments (Terms of Use)

Description Petr Matousek 2012-10-31 17:51:45 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.

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 creating a Bodhi update request, please use the bodhi submission link
noted 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
Bodhi notes field when available.

Please note: this issue affects multiple supported versions of Fedora.
Only one tracking bug has been filed; please ensure that it is only closed
when all affected versions are fixed.

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 Petr Matousek 2012-10-31 17:51:55 UTC
Please use the following update submission link to create the Bodhi
request 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.

Please also ensure that the "Close bugs when update is stable" option
remains checked.

Bodhi update submission link:

Comment 2 Josh Boyer 2012-10-31 18:03:07 UTC
Added the patch to F16-F18.

Comment 3 Fedora Update System 2012-10-31 22:58:42 UTC
kernel-3.6.5-1.fc17 has been submitted as an update for Fedora 17.

Comment 4 Fedora Update System 2012-11-01 02:12:24 UTC
kernel-3.6.5-2.fc18 has been submitted as an update for Fedora 18.

Comment 5 Fedora Update System 2012-11-01 05:53:35 UTC
Package kernel-3.6.5-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.6.5-2.fc18'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2012-11-01 13:23:21 UTC
kernel-3.6.5-2.fc16 has been submitted as an update for Fedora 16.

Comment 7 Adam Williamson 2012-11-01 20:42:37 UTC
Nominating as NTH for F18 Beta; it's a security bug in kernel, that's on the path that can't be fixed entirely by an update (vuln will still be in installer and live images).

Comment 8 Jaroslav Reznik 2012-11-01 20:48:58 UTC
+1 to NTH as it's security issue and can't be fixed by update.

Comment 9 Jóhann B. Guðmundsson 2012-11-01 21:24:07 UTC
+1 to NTH as it's security issue and can't be fixed in the installer without updating the kernel there.

Comment 10 Tim Flink 2012-11-01 21:29:04 UTC
+1 NTH as it's a security issue that can't be fixed by an update

THat makes +4 (assuming +1 from Adam), moving to AcceptedNTH

Comment 11 Adam Williamson 2012-11-08 09:43:32 UTC
We have a much newer kernel stable now, for 17 and 18 at least. Closing. (Bodhi closing of bugs when updates go stable is currently broken).

Comment 12 Josh Boyer 2013-01-02 17:12:22 UTC
*** Bug 866523 has been marked as a duplicate of this bug. ***

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