From 2773b5e236e2217a35a53dbc298757610c7bbbc6 Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Wed, 4 Jun 2025 21:20:13 +0000 Subject: add new iteration --- .../classifier/008/semantic/gitlab_semantic_blsi | 35 ++++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 results/classifier/008/semantic/gitlab_semantic_blsi (limited to 'results/classifier/008/semantic/gitlab_semantic_blsi') diff --git a/results/classifier/008/semantic/gitlab_semantic_blsi b/results/classifier/008/semantic/gitlab_semantic_blsi new file mode 100644 index 000000000..3e01589a9 --- /dev/null +++ b/results/classifier/008/semantic/gitlab_semantic_blsi @@ -0,0 +1,35 @@ +semantic: 0.983 +graphic: 0.873 +device: 0.790 +socket: 0.764 +vnc: 0.756 +boot: 0.678 +network: 0.672 +performance: 0.656 +files: 0.633 +permissions: 0.619 +other: 0.609 +debug: 0.525 +PID: 0.488 +KVM: 0.412 + +x86 BLSI and BLSR semantic bug +Description of problem +The result of instruction BLSI and BLSR is different from the CPU. The value of CF is different. + +Steps to reproduce + +Compile this code + + +void main() { + asm("blsi rax, rbx"); +} + + + +Execute and compare the result with the CPU. The value of CF is exactly the opposite. This problem happens with BLSR, too. + + +Additional information +This bug is discovered by research conducted by KAIST SoftSec. -- cgit 1.4.1