EUVD-2011-2479 · Published Jul 28, 2011
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.
Technologies
Weaknesses
CVSS scores
- v2.01.9
AV:L/AC:M/Au:N/C:P/I:N/A:N
MITRE ATT&CK
InferredWhere this vulnerability fits in an attack
References
- http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=8d03e971cf403305217b8e62db3a2e5ad2d6263f
- http://marc.info/?l=bugtraq&m=139447903326211&w=2
- http://permalink.gmane.org/gmane.linux.bluez.kernel/12909
- http://rhn.redhat.com/errata/RHSA-2011-0927.html
- http://securitytracker.com/id?1025778
- http://www.kernel.org/pub/linux/kernel/v3.0/testing/ChangeLog-3.0-rc4
Potentially impacted assets
See if this affects your attack surface




