Bug 955662 (CVE-2013-3223) - CVE-2013-3223 Kernel: ax25: information leak via msg_name in ax25_recvmsg()
Summary: CVE-2013-3223 Kernel: ax25: information leak via msg_name in ax25_recvmsg()
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2013-3223
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: 955666
Blocks: 858947
TreeView+ depends on / blocked
 
Reported: 2013-04-23 13:35 UTC by Prasad Pandit
Modified: 2021-02-17 07:47 UTC (History)
24 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-09 17:58:52 UTC

Attachments (Terms of Use)

Description Prasad Pandit 2013-04-23 13:35:55 UTC 
Linux kernel built with the Amateur Radio support(CONFIG_HAMRADIO) along with
the Amateur Radio AX.25 Level 2 protocol support enabled 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/ef3313e84acbf349caecae942ab3ab731471f1a1

Reference:
----------
 -> http://www.openwall.com/lists/oss-security/2013/04/14/3
Comment 1 Prasad Pandit 2013-04-23 13:41:22 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-23 13:43:06 UTC 
Created kernel tracking bugs for this issue

Affects: fedora-all [bug 955666]
Comment 3 Fedora Update System 2013-04-27 00:07:38 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:30 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.