From: Andrea Bittau <a.bittau@cs.ucl.ac.uk>
To: netdev@vger.kernel.org
Cc: a.bittau@cs.ucl.ac.uk
Subject: UNIX sockets kernel panic
Date: Thu, 6 Nov 2008 00:14:46 +0000 [thread overview]
Message-ID: <20081106001445.GA5595@shorty> (raw)
The following code causes a kernel panic on Linux 2.6.26:
http://darkircop.org/unix.c
I haven't investigated the bug so I'm not sure what is causing it, and
don't know if it's exploitable. The code passes unix sockets from one
process to another using unix sockets. The bug probably has to do with
closing file descriptors.
[I'm not subscribed to the list so please CC me if you answer.]
next reply other threads:[~2008-11-06 0:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 0:14 Andrea Bittau [this message]
2008-11-06 1:13 ` UNIX sockets kernel panic Alexey Dobriyan
2008-11-06 1:18 ` David Miller
2008-11-06 12:26 ` David Miller
2008-11-06 15:14 ` Andrea Bittau
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=20081106001445.GA5595@shorty \
--to=a.bittau@cs.ucl.ac.uk \
--cc=netdev@vger.kernel.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