First published: Mon Dec 20 2010(Updated: )
Description of problem: In bcm_connect() (in net/can/bcm.c), there is the following code: sprintf(bo->procname, "%p", sock); The CAN protocol uses the address of a kernel heap object sock as a proc filename, revealing information that could be useful during exploitation. Reference: <a href="http://seclists.org/oss-sec/2010/q4/103">http://seclists.org/oss-sec/2010/q4/103</a> <a href="http://www.spinics.net/lists/netdev/msg145791.html">http://www.spinics.net/lists/netdev/msg145791.html</a> Acknowledgements: Red Hat would like to thank Dan Rosenberg for reporting this issue.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/linux-2.6 | ||
debian/user-mode-linux | ||
Linux kernel | <=2.6.36 | |
Linux Kernel | <=2.6.36 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2010-4565 is considered medium due to information disclosure risks.
You can fix CVE-2010-4565 by upgrading to a version of the Linux kernel that is higher than 2.6.36.
CVE-2010-4565 exploits the CAN protocol vulnerability that reveals kernel heap object addresses.
CVE-2010-4565 affects the Linux kernel versions up to and including 2.6.36.
Yes, user-mode-linux is also vulnerable to CVE-2010-4565.