netdev - Re: [PATCH 2/2] dlci: validate the net device in dlci

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20130626.154631.1134375305331643368.davem@davemloft.net>
Date:	Wed, 26 Jun 2013 15:46:31 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	lizefan@...wei.com
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	trinity@...r.kernel.org, lijinyue@...wei.com
Subject: Re: [PATCH 2/2] dlci: validate the net device in dlci_del()

From: Li Zefan <lizefan@...wei.com>
Date: Wed, 26 Jun 2013 15:31:58 +0800

> We triggered an oops while running trinity with 3.4 kernel:
> 
> BUG: unable to handle kernel paging request at 0000000100000d07
> IP: [<ffffffffa0109738>] dlci_ioctl+0xd8/0x2d4 [dlci]
> PGD 640c0d067 PUD 0
> Oops: 0000 [#1] PREEMPT SMP
> CPU 3
> ...
> Pid: 7302, comm: trinity-child3 Not tainted 3.4.24.09+ 40 Huawei Technologies Co., Ltd. Tecal RH2285          /BC11BTSA
> RIP: 0010:[<ffffffffa0109738>]  [<ffffffffa0109738>] dlci_ioctl+0xd8/0x2d4 [dlci]
> ...
> Call Trace:
>   [<ffffffff8137c5c3>] sock_ioctl+0x153/0x280
>   [<ffffffff81195494>] do_vfs_ioctl+0xa4/0x5e0
>   [<ffffffff8118354a>] ? fget_light+0x3ea/0x490
>   [<ffffffff81195a1f>] sys_ioctl+0x4f/0x80
>   [<ffffffff81478b69>] system_call_fastpath+0x16/0x1b
> ...
> 
> It's because the net device is not a dlci device.
> 
> Reported-by: Li Jinyue <lijinyue@...wei.com>
> Signed-off-by: Li Zefan <lizefan@...wei.com>

Applied and queued up for -stable.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html