CVE-2017-1000407

Description

The Linux Kernel 2.6.32 and later are affected by a denial of service, by flooding the diagnostic port 0x80 an exception can be triggered leading to a kernel panic.

Category

7.4
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.46%
Vendor Advisory ubuntu.com Vendor Advisory ubuntu.com Vendor Advisory debian.org Vendor Advisory ubuntu.com Vendor Advisory ubuntu.com Vendor Advisory redhat.com Vendor Advisory ubuntu.com Vendor Advisory redhat.com Vendor Advisory debian.org Vendor Advisory ubuntu.com Vendor Advisory ubuntu.com Vendor Advisory redhat.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://usn.ubuntu.com/3617-1/ third party advisory vendor advisory
https://usn.ubuntu.com/3619-2/ third party advisory vendor advisory
https://www.debian.org/security/2018/dsa-4082 third party advisory vendor advisory
https://lists.debian.org/debian-lts-announce/2017/12/msg00004.html third party advisory mailing list
http://www.openwall.com/lists/oss-security/2017/12/04/2 mailing list third party advisory patch
http://www.securityfocus.com/bid/102038 vdb entry third party advisory
https://usn.ubuntu.com/3583-2/ third party advisory vendor advisory
https://usn.ubuntu.com/3632-1/ third party advisory vendor advisory
https://access.redhat.com/security/cve/cve-2017-1000407 third party advisory
https://access.redhat.com/errata/RHSA-2018:1062 third party advisory vendor advisory
https://usn.ubuntu.com/3583-1/ third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2018:0676 third party advisory vendor advisory
https://www.debian.org/security/2017/dsa-4073 third party advisory vendor advisory
https://usn.ubuntu.com/3617-2/ third party advisory vendor advisory
https://www.spinics.net/lists/kvm/msg159809.html mailing list patch
https://usn.ubuntu.com/3619-1/ third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2019:1170 vendor advisory

Frequently Asked Questions

What is the severity of CVE-2017-1000407?
CVE-2017-1000407 has been scored as a high severity vulnerability.
How to fix CVE-2017-1000407?
To fix CVE-2017-1000407, 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-2017-1000407 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-1000407 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.