From: Pavel Machek <pavel@ucw.cz>
To: marcel@holtmann.org, gustavo@padovan.org,
johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: 3.11-rc2: unpriviledged user crashes kernel using bluetooth
Date: Sat, 31 Aug 2013 12:01:27 +0200 [thread overview]
Message-ID: <20130831100127.GA6711@amd.pavel.ucw.cz> (raw)
Hi!
While trying to set up serial bluetooth connection between two
machines, the server machine died rather hard.
This is what I got on ssh:
Message from syslogd@duo at Aug 31 11:50:07 ...
kernel:Hardware name: LENOVO 17097HU/17097HU, BIOS 7BETD8WW (2.19 )
03/31/2011
Message from syslogd@duo at Aug 31 11:50:07 ...
kernel:task: e6d6a670 ti: e8fd8000 task.ti: e8fd8000
Message from syslogd@duo at Aug 31 11:50:07 ...
kernel:Stack:
Message from syslogd@duo at Aug 31 11:50:07 ...
kernel:Call Trace:
Message from syslogd@duo at Aug 31 11:50:07 ...
kernel:Code: 66 ff ff ff eb b9 ba 79 c9 b6 c0 89 d8 e8 58 ff ff ff eb
a0 8d b6 00 00 00 00 55 89 e5 83 ec 10 89 5d f4 89 c3 89 75 f8 89 7d
fc <81> 78 04 ad 4e ad de 0f 85 11 01 00 00 64 a1 4c 87 d2 c0 39 43
Message from syslogd@duo at Aug 31 11:50:07 ...
kernel:EIP: [<c04621f1>] do_raw_spin_lock+0x11/0x140 SS:ESP
0068:e8fd9e0c
Message from syslogd@duo at Aug 31 11:50:07 ...
kernel:CPU: 0 PID: 3822 Comm: modem-manager Tainted: G D W
3.11.0-rc2+ #306
Message from syslogd@duo at Aug 31 11:50:07 ...
kernel:Hardware name: LENOVO 17097HU/17097HU, BIOS 7BETD8WW (2.19 )
03/31/2011
Message from syslogd@duo at Aug 31 11:50:07 ...
kernel:task: e6d9a670 ti: e6d4e000 task.ti: e6d4e000
Message from syslogd@duo at Aug 31 11:50:07 ...
kernel:Stack:
Message from syslogd@duo at Aug 31 11:50:07 ...
kernel:Call Trace:
Message from syslogd@duo at Aug 31 11:50:07 ...
kernel:Code: 66 ff ff ff eb b9 ba 79 c9 b6 c0 89 d8 e8 58 ff ff ff eb
a0 8d b6 00 00 00 00 55 89 e5 83 ec 10 89 5d f4 89 c3 89 75 f8 89 7d
fc <81> 78 04 ad 4e ad de 0f 85 11 01 00 00 64 a1 4c 87 d2 c0 39 43
Message from syslogd@duo at Aug 31 11:50:07 ...
kernel:EIP: [<c04621f1>] do_raw_spin_lock+0x11/0x140 SS:ESP
0068:e6d4fe0c
. 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.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next reply other threads:[~2013-08-31 10:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 10:01 Pavel Machek [this message]
2013-08-31 10:09 ` 3.11-rc2: unpriviledged user crashes kernel using bluetooth Pavel Machek
2013-08-31 10:12 ` 3.10: " Pavel Machek
2013-08-31 10:14 ` 3.11-rc2: " Pavel Machek
2013-08-31 10:42 ` 3.11-rc7: " Pavel Machek
2013-09-01 16:55 ` Gustavo Padovan
2013-09-01 18:50 ` 3.11-final plan: unpriviledged user can crash the kernel (using bluetooth rfcomm) Pavel Machek
2013-09-01 20:16 ` Marcel Holtmann
2013-09-01 22:12 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130831100127.GA6711@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).