From d760c82f4244dc47f5413c3c88b640bb1f0f2d9e Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Tue, 3 Jun 2025 14:41:43 +0200 Subject: move semantic_issues dir to results --- .../gitlab/semantic_issues/gitlab_semantic_blsmsk | 27 ++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 results/scraper/gitlab/semantic_issues/gitlab_semantic_blsmsk (limited to 'results/scraper/gitlab/semantic_issues/gitlab_semantic_blsmsk') diff --git a/results/scraper/gitlab/semantic_issues/gitlab_semantic_blsmsk b/results/scraper/gitlab/semantic_issues/gitlab_semantic_blsmsk new file mode 100644 index 00000000..b950faa2 --- /dev/null +++ b/results/scraper/gitlab/semantic_issues/gitlab_semantic_blsmsk @@ -0,0 +1,27 @@ +x86 BLSMSK semantic bug +Description of problem +The result of instruction BLSMSK is different with from the CPU. The value of CF is different. + +Steps to reproduce + +Compile this code + +void main() { + asm("mov rax, 0x65b2e276ad27c67"); + asm("mov rbx, 0x62f34955226b2b5d"); + asm("blsmsk eax, ebx"); +} + +Execute and compare the result with the CPU. + +CPU + +CF = 0 + + +QEMU + +CF = 1 + +Additional information +This bug is discovered by research conducted by KAIST SoftSec. -- cgit 1.4.1