VirtualBox

Opened 7 years ago

Last modified 7 years ago

#17481 new defect

VM crashes when allocating memory at MSR_LSTAR address range

Reported by: D1W0U Owned by:
Component: other Version: VirtualBox 5.2.6
Keywords: MSR_LSTAR, LKM, SYSCALL, memory-allocation, range, crash Cc:
Guest type: Linux Host type: Windows

Description

Hi,

I'm developing a Linux LKM, and I tried to reserve memory in the same range of MSR_LSTAR (SYSCALL handler), with vmalloc_node_range().

On the 3rd execution of that function, returning first NULL, second an address and third time NULL, the Guru Mediation spawns.

I'm attaching the source code to reproduce the bug, the log and the screenshot.

Thanks for help.

Attachments (3)

crash virtualbox coding arprk.png (95.0 KB ) - added by D1W0U 7 years ago.
recopilation of the bug in a image
VBox.log (90.3 KB ) - added by D1W0U 7 years ago.
crash log
vbox_crash.zip (976 bytes ) - added by D1W0U 7 years ago.
LKM to reproduce the crash

Download all attachments as: .zip

Change History (4)

by D1W0U, 7 years ago

recopilation of the bug in a image

by D1W0U, 7 years ago

Attachment: VBox.log added

crash log

by D1W0U, 7 years ago

Attachment: vbox_crash.zip added

LKM to reproduce the crash

comment:1 by D1W0U, 7 years ago

seems the VM cpu(s) memory is zeroed when allocating in its range as I can see the range for cpu_area_entry_mapping in linux-hwe-4.13.0/Documentation/x86/x86_64/mm.txt:fffffe8000000000 - fffffeffffffffff (=39 bits) cpu_entry_area mapping

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use