Summary: | sys-kernel/hardened-sources-2.6.36-r6: panic when running app-emulation/virtualbox-ose-3.2.12-r1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Anthony Basile <blueness> |
Component: | Hardened | Assignee: | The Gentoo Linux Hardened Kernel Team (OBSOLETE) <hardened-kernel+disabled> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | hardened, pageexec, seraph, spender |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 350475 |
Description
Anthony Basile
2011-01-03 23:45:56 UTC
(In reply to comment #0) > When running VirtualBox 3.2.12, the GUI starts up fine, but as soon as one > starts a vm. Using netconsole, I caught the panic from an amd64 box: > Jan 3 17:08:20 yellowness RIP > Jan 3 17:08:20 yellowness [<ffffffffa08f1297>] g_abExecMemory+0xa297/0x18490c > [vboxdrv] > Jan 3 17:08:20 yellowness RSP <ffff88031a0f7b40> > Jan 3 17:08:20 yellowness CR2: ffffffff81681044 this is some vbox code trying to modify read-only memory under KERNEXEC, probably something in the GDT (you can check where rax falls based on System.map). so you can either disable KERNEXEC or find the offending code in one of the runtime loaded vbox modules and add the proper open/close kernel annotations. i don't quite feel like hunting this down myself, so feel free to let upstream figure it out ;). > > so feel free to > let upstream figure it out ;). > Reported upstream: http://www.virtualbox.org/ticket/7996 Currently this bug is being mitigated in hardened-gentoo by disabling KERNEXEC via the predefined grsec/pax configuration VIRTUALIZATION. I'll leave this bug open in the off chance that upstream might act on it. Probably related: If CONFIG_DEBUG_SET_MODULE_RONX is set, the kernel panics as soon as the VirtualBox modules are loaded. hardened-sources-2.6.36-r6 was just removed from the tree. |