kernel infoleak detected!

Discuss usability issues, general maintenance, and general support issues for a grsecurity-enabled system.

kernel infoleak detected!

Postby brainatwork » Tue Dec 18, 2012 4:30 pm

Hi Spender

I detect this message on my box (running gentoo 3.5.4-hardened-r1).
Do you need anything else? .config?

grsec: kernel infoleak detected! Please report this log to spender@grsecurity.net.
Pid: 3591, comm: xenstored Not tainted 3.5.4-hardened-r1-io-dom0-gw02 #1
Call Trace:
[<ffffffff812521d5>] pointer.clone.10+0x2e2/0x32b
[<ffffffff81129945>] ? proc_mkdir_mode+0x3e/0x57
[<ffffffff81251cc1>] vsnprintf+0x21c/0x44e
[<ffffffff81254d6b>] kvasprintf+0x5f/0x70
[<ffffffff812c87ae>] ? xsd_port_open+0x3a/0x3a
[<ffffffff81254db5>] kasprintf+0x39/0x3c
[<ffffffff812c87d5>] xsd_kva_open+0x27/0x3b
[<ffffffff810da0bc>] do_dentry_open+0x15c/0x221
[<ffffffff810daf0e>] nameidata_to_filp+0x5a/0xa0
[<ffffffff810e826b>] do_last+0xa52/0xa66
[<ffffffff810e8348>] path_openat+0xc9/0x3b0
[<ffffffff812486bc>] ? gr_log_resource+0x20/0xfc
[<ffffffff810e8668>] do_filp_open+0x39/0x86
[<ffffffff810f44a8>] ? expand_files+0x3a/0x19b
[<ffffffff810f48a5>] ? alloc_fd+0x70/0x100
[<ffffffff810db372>] do_sys_open+0x118/0x1ab
[<ffffffff810db421>] sys_open+0x1c/0x1e
[<ffffffff815f8940>] system_call_fastpath+0x18/0x1d

hardware is: Intel(R) Atom(TM) CPU N2800 @ 1.86GHz (intel n2800dmt board)
brainatwork
 
Posts: 23
Joined: Wed Aug 13, 2008 12:53 pm

Re: kernel infoleak detected!

Postby KDE » Tue Dec 18, 2012 5:15 pm

kernel 3.5 is probably unsupported
try 3.7.1 or 3.2.35
http://grsecurity.net/test.php
KDE
 
Posts: 57
Joined: Sat Feb 09, 2008 5:29 am

Re: kernel infoleak detected!

Postby PaX Team » Tue Dec 18, 2012 6:03 pm

the same code is present in 3.7 as well (and possibly earlier kernels too, i didn't check those), so he'll take a look and fix this.
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm

Re: kernel infoleak detected!

Postby spender » Wed Dec 19, 2012 8:39 am

This was already fixed in a previous kernel (and is still fixed in 3.7.1).

-Brad
spender
 
Posts: 2185
Joined: Wed Feb 20, 2002 8:00 pm


Return to grsecurity support