summary refs log tree commit diff stats
path: root/results/scraper/gitlab/semantic_issues/gitlab_semantic_bextr
diff options
context:
space:
mode:
Diffstat (limited to 'results/scraper/gitlab/semantic_issues/gitlab_semantic_bextr')
-rw-r--r--results/scraper/gitlab/semantic_issues/gitlab_semantic_bextr25
1 files changed, 25 insertions, 0 deletions
diff --git a/results/scraper/gitlab/semantic_issues/gitlab_semantic_bextr b/results/scraper/gitlab/semantic_issues/gitlab_semantic_bextr
new file mode 100644
index 00000000..dabe16ac
--- /dev/null
+++ b/results/scraper/gitlab/semantic_issues/gitlab_semantic_bextr
@@ -0,0 +1,25 @@
+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.