This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected Fedora
For comments that are specific to the vulnerability please use bugs filed
against "Security Response" product referenced in the "Blocks" field.
For more information see:
When creating a Bodhi update request, please include this bug ID and the
bug IDs of this bug's parent bugs filed against the "Security Response"
product (the top-level CVE bugs). Please mention the CVE IDs being fixed
in the RPM changelog when available.
Bodhi update submission link:
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]
It seems Linus doesn't want to take the patches for 3.2 at all. I'm somewhat inclined to agree for now.
The patches went into what will be 3.3, so they will be picked up when rawhide is rebased.
Paolo sent backported patches to the stable branches, but they missed the 3.1.10 cutoff (will be in 3.2.2 from what I saw). I've applied them to the F15/F16 branches.
kernel-3.2.1-3.fc16 has been submitted as an update for Fedora 16.
kernel-18.104.22.168-3.fc15 has been submitted as an update for Fedora 15.
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-22.214.171.124-3.fc15'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
kernel-3.2.1-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
kernel-126.96.36.199-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.