Bug 956125 (CVE-2013-3233) - CVE-2013-3233 Kernel: NFC: llcp: info leaks via msg_name in llcp_sock_recvmsg
Summary: CVE-2013-3233 Kernel: NFC: llcp: info leaks via msg_name in llcp_sock_recvmsg
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2013-3233
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 956129
Blocks: 858947
TreeView+ depends on / blocked
 
Reported: 2013-04-24 10:24 UTC by Prasad Pandit
Modified: 2021-02-17 07:46 UTC (History)
24 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-09 18:11:35 UTC
Embargoed:

Attachments (Terms of Use)

Description Prasad Pandit 2013-04-24 10:24:30 UTC 
Linux kernel built with the Near Field Communication(CONFIG_NFC) subsystem
along with the Logical Link Control Protocol(CONFIG_NFC_LLCP) support is
vulnerable to an information leakage flaw. It occurs while receiving messages
via recvmsg(2) call.

A user/program could use this flaw to leak kernel memory bytes.

Upstream fix:
-------------
 -> http://git.kernel.org/linus/d26d6504f23e803824e8ebd14e52d4fc0a0b09cb

Reference:
----------
 -> http://www.openwall.com/lists/oss-security/2013/04/14/3
Comment 1 Prasad Pandit 2013-04-24 10:27:58 UTC 
Statement:

This issue does not affect the versions of the kernel package as shipped with
Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2.
Comment 2 Prasad Pandit 2013-04-24 10:29:26 UTC 
Created kernel tracking bugs for this issue

Affects: fedora-all [bug 956129]
Comment 3 Fedora Update System 2013-04-27 00:08:05 UTC 
kernel-3.8.8-203.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 4 Fedora Update System 2013-05-04 00:08:00 UTC 
kernel-3.8.11-100.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.