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]
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=1295480,1295482 # Description of your update notes=Security fix for # 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=1295480,1295482
a root access is needed on a virtual machines with SRIOV network card's VF allocated to disturb communications of other VMs on the same host which use the same SRIOV network card. the problem i see here is that every driver for SRIOV cards should be checked/modified, to properly close this, not a kernel code. there are fixes for intel and broadcom cards (see http://seclists.org/oss-sec/2015/q4/425), but no CVE assigned since Dec 3 2015. looks more like a security hardening than security issue.
I agree with Vladis' assessment. The fixes for this will come in piecemeal through individual drivers or in some cases through device firmware updates. After discussing with the rest of the kernel team, we are closing this as upstream.