CVE-2005-3276

Description

The sys_get_thread_area function in process.c in Linux 2.6 before 2.6.12.4 and 2.6.13 does not clear a data structure before copying it to userspace, which might allow a user process to obtain sensitive information.

2.1

CVSS

Severity: Low

CVSS 2.0 •

EPSS 0.11%

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

Affected: n/a n/a

References

Link	Tags
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A9748	vdb entry signature
http://secunia.com/advisories/18056	third party advisory
http://www.mandriva.com/security/advisories?name=MDKSA-2005:220	vendor advisory
http://www.redhat.com/support/errata/RHSA-2006-0144.html	vendor advisory
http://www.redhat.com/support/errata/RHSA-2006-0101.html	vendor advisory
http://www.securityfocus.com/bid/15527	vdb entry
http://lkml.org/lkml/2005/8/3/36
http://www.securityfocus.com/archive/1/428058/100/0/threaded	vendor advisory
http://www.debian.org/security/2005/dsa-922	vendor advisory
https://usn.ubuntu.com/219-1/	vendor advisory
http://secunia.com/advisories/18510	third party advisory
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=71ae18ec690953e9ba7107c7cc44589c2cc0d9f1
http://www.mandriva.com/security/advisories?name=MDKSA-2005:218	vendor advisory
http://www.securityfocus.com/archive/1/428028/100/0/threaded	vendor advisory
http://secunia.com/advisories/17826	third party advisory
http://www.securityfocus.com/archive/1/427980/100/0/threaded	vendor advisory
http://www.mandriva.com/security/advisories?name=MDKSA-2005:219	vendor advisory
http://secunia.com/advisories/19252	third party advisory
http://linux.bkbits.net:8080/linux-2.6/cset%4042e81864gSEM90Oun0jA8dufpM3inw

Frequently Asked Questions

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