Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1826350

Summary: [Microsoft driver security checklist] Review debugger techniques and extensions for virtio-win drivers
Product: Red Hat Enterprise Linux 8 Reporter: Yvugenfi <yvugenfi>
Component: virtio-winAssignee: Amnon Ilan <ailan>
virtio-win sub component: virtio-win-prewhql QA Contact: Peixiu Hou <phou>
Status: CLOSED NOTABUG Docs Contact:
Severity: medium    
Priority: unspecified CC: jinzhao, juzhang, lijin, phou
Version: 8.3Keywords: TestOnly
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-26 08:28:07 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1826331    

Comment 3 Peixiu Hou 2020-04-23 10:10:56 UTC 
Hi Yan,

I tried to run command !exploitable, but report error "No export exploitable found", as follows:
==============================
0: kd> !exploitable
No export exploitable found
==============================

I tried install Visual C++ Redistributable for Visual Studio 2012(https://www.microsoft.com/en-us/download/details.aspx?id=30679) and http://download.microsoft.com/download/A/6/A/A6AC035D-DA3F-4F0C-ADA4-37C8E5D34E3D/setup/WinSDKDebuggingTools/dbg_x86.msi, but also cannot work.
I used windbg version is 10.0.16299.15

My steps:
1. Open the WinDbg tool.
2. Open File --> SymbolFile Path...
3. Add Symbol path: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols 
4. Open File --> Open Crash Dump...
5. Choose need analyzed Memory.dmp file
6. Execute 0: kd> !analyze -v
   command can be run normally, but report follows message:
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

------------------------------------------------------
|                                                    |
|            NT symbols are not available            |
|   Kernel hints available (reduced functionality)   |
|                                                    |
------------------------------------------------------
<Unable to get nt!KiCurrentEtwBufferOffset><Unable to get nt!KiCurrentEtwBufferBase>******
7. Eecute 0: kd> !exploitable, report error "No export exploitable found"

Could you help to check if any steps I missed or incorrect? 

Thanks a lot~
Peixiu