CVE-2015-8816

Description

The hub_activate function in drivers/usb/core/hub.c in the Linux kernel before 4.3.5 does not properly maintain a hub-interface data structure, which allows physically proximate attackers to cause a denial of service (invalid memory access and system crash) or possibly have unspecified other impact by unplugging a USB hub device.

6.8

CVSS

Severity: Medium

CVSS 3.1 •

CVSS 2.0 •

EPSS 0.08%

Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory debian.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory kernel.org Vendor Advisory kernel.org Vendor Advisory github.com

Affected: n/a n/a

References

Link	Tags
http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00054.html	third party advisory vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00022.html	third party advisory vendor advisory
https://github.com/torvalds/linux/commit/e50293ef9775c5f1cf3fcc093037dd6a8c5684ea	patch vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00008.html	third party advisory vendor advisory
http://www.oracle.com/technetwork/topics/security/linuxbulletinjul2016-3090544.html	third party advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00003.html	third party advisory vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00015.html	third party advisory vendor advisory
http://www.debian.org/security/2016/dsa-3503	third party advisory vendor advisory
http://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.3.5	vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00019.html	third party advisory vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00026.html	third party advisory vendor advisory
http://www.securityfocus.com/bid/83363	third party advisory vdb entry
http://lists.opensuse.org/opensuse-security-announce/2016-07/msg00005.html	third party advisory vendor advisory
https://bugzilla.redhat.com/show_bug.cgi?id=1311589	issue tracking
http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00059.html	third party advisory vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00052.html	third party advisory vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00019.html	third party advisory vendor advisory
http://source.android.com/security/bulletin/2016-07-01.html	third party advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00021.html	third party advisory vendor advisory
http://www.openwall.com/lists/oss-security/2016/02/23/5	mailing list
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00018.html	third party advisory vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00020.html	third party advisory vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00038.html	third party advisory vendor advisory
http://www.oracle.com/technetwork/topics/security/ovmbulletinoct2016-3090547.html	third party advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00009.html	third party advisory vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00016.html	third party advisory vendor advisory
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e50293ef9775c5f1cf3fcc093037dd6a8c5684ea	vendor advisory

Frequently Asked Questions

What is the severity of CVE-2015-8816?: CVE-2015-8816 has been scored as a medium severity vulnerability.
How to fix CVE-2015-8816?: To fix CVE-2015-8816, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2015-8816 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2015-8816 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.