From 3e4c5a6261770bced301b5e74233e7866166ea5b Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Sun, 1 Jun 2025 21:35:14 +0200 Subject: clean up repository --- .../03/semantic/gitlab_semantic_bextr | 33 ---------------------- 1 file changed, 33 deletions(-) delete mode 100644 classification_output/03/semantic/gitlab_semantic_bextr (limited to 'classification_output/03/semantic/gitlab_semantic_bextr') diff --git a/classification_output/03/semantic/gitlab_semantic_bextr b/classification_output/03/semantic/gitlab_semantic_bextr deleted file mode 100644 index ba7f4513f..000000000 --- a/classification_output/03/semantic/gitlab_semantic_bextr +++ /dev/null @@ -1,33 +0,0 @@ -semantic: 0.993 -instruction: 0.944 -boot: 0.516 -mistranslation: 0.337 -network: 0.219 -other: 0.099 -KVM: 0.091 - -x86 BEXTR semantic bug -Description of problem -The result of instruction BEXTR is different with from the CPU. The value of destination register is different. I think QEMU does not consider the operand size limit. - -Steps to reproduce - -Compile this code - -void main() { - asm("mov rax, 0x17b3693f77fb6e9"); - asm("mov rbx, 0x8f635a775ad3b9b4"); - asm("mov rcx, 0xb717b75da9983018"); - asm("bextr eax, ebx, ecx"); -} - -Execute and compare the result with the CPU. - -CPU -RAX = 0x5a - -QEMU -RAX = 0x635a775a - -Additional information -This bug is discovered by research conducted by KAIST SoftSec. -- cgit 1.4.1