CVE-2016-6480

Description

Race condition in the ioctl_send_fib function in drivers/scsi/aacraid/commctrl.c in the Linux kernel through 4.7 allows local users to cause a denial of service (out-of-bounds access or system crash) by changing a certain size value, aka a "double fetch" vulnerability.

Category

5.1
CVSS
Severity: Medium
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.06%
Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://bugzilla.redhat.com/show_bug.cgi?id=1362466 third party advisory vdb entry issue tracking
http://www.securityfocus.com/archive/1/539074/30/0/threaded mailing list third party advisory vdb entry
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00053.html vendor advisory
http://www.securityfocus.com/bid/92214 vdb entry
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00048.html vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-09/msg00001.html vendor advisory
http://rhn.redhat.com/errata/RHSA-2016-2584.html vendor advisory
http://rhn.redhat.com/errata/RHSA-2016-2574.html vendor advisory
http://rhn.redhat.com/errata/RHSA-2017-0817.html vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00054.html vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00051.html vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00049.html vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00050.html vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00052.html vendor advisory

Frequently Asked Questions

What is the severity of CVE-2016-6480?
CVE-2016-6480 has been scored as a medium severity vulnerability.
How to fix CVE-2016-6480?
To fix CVE-2016-6480, 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-2016-6480 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2016-6480 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.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.