CVE-2005-1762

Description

The ptrace call in the Linux kernel 2.6.8.1 and 2.6.10 for the AMD64 platform allows local users to cause a denial of service (kernel crash) via a "non-canonical" address.

2.1

CVSS

Severity: Low

CVSS 2.0 •

EPSS 0.06%

Vendor Advisory securityfocus.com Vendor Advisory novell.com Vendor Advisory debian.org Vendor Advisory debian.org Vendor Advisory redhat.com Vendor Advisory ubuntu.com Vendor Advisory securityfocus.com Vendor Advisory redhat.com Vendor Advisory secunia.com

Affected: n/a n/a

References

Link	Tags
http://secunia.com/advisories/18056	third party advisory
http://secunia.com/advisories/17073	third party advisory
http://www.securityfocus.com/bid/13904	vdb entry
http://secunia.com/advisories/18059	third party advisory
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10630	vdb entry signature
http://www.securityfocus.com/archive/1/428058/100/0/threaded	vendor advisory
http://www.novell.com/linux/security/advisories/2005_29_kernel.html	patch vendor advisory
http://www.debian.org/security/2005/dsa-922	vendor advisory
http://secunia.com/advisories/15786	third party advisory patch vendor advisory
http://www.debian.org/security/2005/dsa-921	vendor advisory
http://www.redhat.com/support/errata/RHSA-2005-514.html	vendor advisory
http://secunia.com/advisories/17002	third party advisory
https://usn.ubuntu.com/143-1/	vendor advisory
http://www.securityfocus.com/archive/1/427980/100/0/threaded	vendor advisory
http://www.redhat.com/support/errata/RHSA-2005-663.html	vendor advisory
http://www.vupen.com/english/advisories/2005/1878	vdb entry

Frequently Asked Questions

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