CVE-2006-2448

Description

Linux kernel before 2.6.16.21 and 2.6.17, when running on PowerPC, does not perform certain required access_ok checks, which allows local users to read arbitrary kernel memory on 64-bit systems (signal_64.c) and cause a denial of service (crash) and possibly read kernel memory on 32-bit systems (signal_32.c).

5.6

CVSS

Severity: Medium

CVSS 2.0 •

EPSS 0.06%

Vendor Advisory novell.com Vendor Advisory novell.com Vendor Advisory trustix.org Vendor Advisory redhat.com Vendor Advisory ubuntu.com

Affected: n/a n/a

References

Link	Tags
http://secunia.com/advisories/20703	third party advisory
http://www.vupen.com/english/advisories/2006/2451	vdb entry
http://www.novell.com/linux/security/advisories/2006_42_kernel.html	vendor advisory
http://www.securityfocus.com/archive/1/438168/100/0/threaded	mailing list
http://www.novell.com/linux/security/advisories/2006_47_kernel.html	vendor advisory
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10040	signature vdb entry
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=7c85d1f9d358b24c5b05c3a2783a78423775a080
http://www.trustix.org/errata/2006/0037	vendor advisory
http://www.redhat.com/support/errata/RHSA-2006-0575.html	vendor advisory
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=194215
http://www.ubuntu.com/usn/usn-311-1	vendor advisory
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.16.21
http://secunia.com/advisories/21465	third party advisory
http://secunia.com/advisories/20831	third party advisory
http://secunia.com/advisories/21498	third party advisory
http://www.securityfocus.com/bid/18616	patch vdb entry
http://support.avaya.com/elmodocs2/security/ASA-2006-200.htm
http://secunia.com/advisories/22417	third party advisory
http://secunia.com/advisories/20991	third party advisory
http://secunia.com/advisories/21179	third party advisory

Frequently Asked Questions

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