Description
The bluetooth subsystem in the Linux kernel before 3.0-rc4 does not properly initialize certain data structures, which allows local users to obtain potentially sensitive information from kernel memory via a crafted getsockopt system call, related to (1) the l2cap_sock_getsockopt_old function in net/bluetooth/l2cap_sock.c and (2) the rfcomm_sock_getsockopt_old function in net/bluetooth/rfcomm/sock.c.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
n/a n/a
n/aaffected
References
- http://rhn.redhat.com/errata/RHSA-2011-0927.html ↗
- http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=8d03e971cf403305217b8e62db3a2e5ad2d6263f ↗
- https://bugzilla.redhat.com/show_bug.cgi?id=703019 ↗
- http://www.kernel.org/pub/linux/kernel/v3.0/testing/ChangeLog-3.0-rc4 ↗
- http://www.openwall.com/lists/oss-security/2011/06/24/3 ↗
- http://securitytracker.com/id?1025778 ↗
- http://www.openwall.com/lists/oss-security/2011/06/24/2 ↗
- http://permalink.gmane.org/gmane.linux.bluez.kernel/12909 ↗
- http://marc.info/?l=bugtraq&m=139447903326211&w=2 ↗