CVE-2006-0557

Description

sys_mbind in mempolicy.c in Linux kernel 2.6.16 and earlier does not sanity check the maxnod variable before making certain computations for the get_nodes function, which has unknown impact and attack vectors.

4.9

CVSS

Severity: Medium

CVSS 2.0 •

EPSS 0.06%

Vendor Advisory ubuntu.com Vendor Advisory novell.com Vendor Advisory debian.org Vendor Advisory redhat.com Vendor Advisory mandriva.com

Affected: n/a n/a

References

Link	Tags
http://securitytracker.com/id?1015752	vdb entry
http://www.vupen.com/english/advisories/2006/2554	vdb entry
https://usn.ubuntu.com/281-1/	vendor advisory
http://www.osvdb.org/23895	vdb entry
http://lkml.org/lkml/2006/2/27/355
http://www.securityfocus.com/bid/16924	vdb entry
https://exchange.xforce.ibmcloud.com/vulnerabilities/25204	vdb entry
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=636f13c174dd7c84a437d3c3e8fa66f03f7fda63
http://www.novell.com/linux/security/advisories/2006-05-31.html	vendor advisory
http://secunia.com/advisories/19955	third party advisory
http://www.debian.org/security/2006/dsa-1103	vendor advisory
http://rhn.redhat.com/errata/RHBA-2007-0304.html	vendor advisory
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=184510
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commitdiff%3Bh=636f13c174dd7c84a437d3c3e8fa66f03f7fda63
http://secunia.com/advisories/20398	third party advisory
http://www.mandriva.com/security/advisories?name=MDKSA-2006:059	vendor advisory
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A9674	vdb entry signature
http://secunia.com/advisories/20914	third party advisory

Frequently Asked Questions

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