device: 0.810
vnc: 0.649
network: 0.605
socket: 0.550
graphic: 0.529
semantic: 0.472
performance: 0.439
permissions: 0.389
boot: 0.377
other: 0.354
PID: 0.326
files: 0.287
debug: 0.190
KVM: 0.162

Information leak in IDE core

When the DRQ_STAT bit is set, the IDE core permits both data reads and data writes, regardless of whether the current transfer was initiated as a read or write.

Furthermore, the IO buffer is allocated via a qemu_memalign but not initialized or cleared at device creation.

This potentially leaks uninitialized host memory into the guest, if, before doing anything else to an IDE device, the guest begins a write transaction (e.g. WIN_WRITE), but then *reads* from the IO port instead of writing to it. The IDE core will happily return the uninitialized contents of the buffer to the guest, potentially leaking offsets that could be used as part of an attack to get around ASLR.

hi Nelson :
    
    what 's the flag 'DRQ_STAT' mean for   HD_STATUS ?

Fixed here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=40c4ed3f95f0b2ffa0848df0f