Bug 649713 (CVE-2010-3875) - CVE-2010-3875 kernel: net/ax25/af_ax25.c: reading uninitialized stack memory
Summary: CVE-2010-3875 kernel: net/ax25/af_ax25.c: reading uninitialized stack memory
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2010-3875
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-04 12:01 UTC by Petr Matousek
Modified: 2023-05-11 15:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-19 09:15:34 UTC
Embargoed:


Attachments (Terms of Use)

Description Petr Matousek 2010-11-04 12:01:54 UTC
Description of problem:
Sometimes ax25_getname() doesn't initialize all members of fsa_digipeater field of fsa struct.  This structure is then copied to userland.  It leads to leaking of contents of kernel stack memory.  We have to initialize them to zero.

Reference:
http://marc.info/?l=linux-netdev&m=128854507120898&w=2
http://seclists.org/oss-sec/2010/q4/94

Acknowledgements:

Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue.

Comment 1 Petr Matousek 2010-11-04 18:46:29 UTC
Statement:

This issue did not affect the version of Linux kernel as shipped with Red Hat
Enterprise Linux 4, 5, and Red Hat Enterprise MRG as they did not include
support for Amateur Radio AX.25 protocol.

This issue is not planned to be fixed in Red Hat Enterprise Linux 3, due to
this product being in Extended Life Cycle Phase of its maintenance life-cycle,
where only qualified security errata of critical impact are addressed.

For further information about the Errata Support Policy, visit:
http://www.redhat.com/security/updates/errata

Comment 2 Eugene Teo (Security Response) 2010-11-22 13:22:42 UTC
Upstream commit:
http://git.kernel.org/linus/fe10ae53384e48c51996941b7720ee16995cbcb7


Note You need to log in before you can comment on or make changes to this bug.