kernel panic

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

kernel panic

Postby rom2mars » Fri Feb 07, 2014 11:14 am

Hello,

I have a problem with kernel panic when I try to communicate with my moxa driver.

The problem occurs only when the kernel is compiled with grsecurity.

Image

I use kernel 3.2.54

I use the moxa driver :
http://www.moxa.com/support/DownloadFil ... ort&id=952

regards,
Romain
rom2mars
 
Posts: 16
Joined: Fri Feb 07, 2014 10:52 am

Re: kernel panic

Postby PaX Team » Fri Feb 07, 2014 12:29 pm

can you somehow capture the full oops log? (serial or netconsole perhaps) also enable frame pointers for a better backtrace. if all else fails, you could try using a framebuffer console that can fit more information on the screen.
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm

Re: kernel panic

Postby PaX Team » Fri Feb 07, 2014 12:35 pm

ok, after a very quick look i think this is the culprit in moxa/npreal2.c:npreal_net_write:

Code: Select all
if ((count = tty_insert_flip_string(tty, (unsigned char *)buf, cnt)))


if i'm not mistaken, buf is a userland provided pointer here and should go through copy_from_user or similar (like the other side of the #ifdef does) instead of being directly passed to tty_insert_flip_string. you probably had UDEREF enabled which catches these kinds of bugs (it's probably some kind of security bug too, better let upstream know).
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm

Re: kernel panic

Postby rom2mars » Fri Feb 14, 2014 8:39 am

Thank you very much.
rom2mars
 
Posts: 16
Joined: Fri Feb 07, 2014 10:52 am


Return to grsecurity support