This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
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]
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
Bodhi update submission link:
Fixed in git.
kernel-3.13.8-200.fc20 has been submitted as an update for Fedora 20.
kernel-3.13.8-100.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.13.8-100.fc19'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
Josh, there is v2 of the advisory that mentions that the original patch did not fix the issue. The latest patch is https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=e9d8b2c2968499c1f96563e6522c56958d5a1d0d.
I think we're OK with the patch committed to Fedora. The v2 of the advisory talks about calling xenvif_carrier_off from an invalid context and deferring it to a kthread instead. The patch I picked up already does that (it was v2 of the patch).
It only differs from the commit you point to in one area, which is calling napi_complete instead of doing the local_irq_save/__napi_complete/local_irq_restore dance. That should be a fairly minor implementation detail. We'll pick up the upstream commit when it gets backported to stable, but we should be OK from an CVE perspective.
kernel-3.13.8-200.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
kernel-3.13.9-100.fc19 has been submitted as an update for Fedora 19.
kernel-3.13.9-100.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.