linux-kernel - Re: 3.11-rc2: unpriviledged user crashes kernel using bluetooth

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sat, 31 Aug 2013 12:09:33 +0200
From:	Pavel Machek <pavel@....cz>
To:	marcel@...tmann.org, gustavo@...ovan.org, johan.hedberg@...il.com,
	linux-bluetooth@...r.kernel.org,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: 3.11-rc2: unpriviledged user crashes kernel using bluetooth

Hi!

> . Python sources for client/server are at 
> 
> http://tui.cvs.sourceforge.net/viewvc/tui/tui/liveview/
> 
> . My kernels like to warn about
> 
> Aug 31 11:46:37 duo kernel: WARNING: CPU: 1 PID: 1 at
> net/wireless/reg.c:423 regulatory_init+0x92/0xff()
> Aug 31 11:46:37 duo kernel: db.txt is empty, you should update it...
> 
> . 3.10 does not seem to be affected.

When I said 3.10 was not affected, I was wrong. 3.10 survived the
test, but when I attempted to reboot the box, I got 

WARNING: at lib/list_debug.c:59 __list_del_entry+0xac/0xe0()
list_del_corruption. prev->next should be f44fffd4, but was f44c402c
...
...Comm: bluetoothd....
Call trace:
...
__list_del_entry
cd_forget
evict
iput

System is debian stable with gnome2.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/