summary refs log tree commit diff stats
path: root/results/classifier/zero-shot-user-mode/output/instruction/1880332
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-07 17:23:11 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-07 17:23:11 +0000
commitc50b0c4da17b6e83640e4ed2380fffb5f507c846 (patch)
treeb4f203fce1380e2ea3578a784bb8ee060fe42cbd /results/classifier/zero-shot-user-mode/output/instruction/1880332
parent61361f925d4914a6608a0076e64cc2399311ed5f (diff)
downloadqemu-analysis-c50b0c4da17b6e83640e4ed2380fffb5f507c846.tar.gz
qemu-analysis-c50b0c4da17b6e83640e4ed2380fffb5f507c846.zip
add zero-shot results
Diffstat (limited to 'results/classifier/zero-shot-user-mode/output/instruction/1880332')
-rw-r--r--results/classifier/zero-shot-user-mode/output/instruction/188033213
1 files changed, 13 insertions, 0 deletions
diff --git a/results/classifier/zero-shot-user-mode/output/instruction/1880332 b/results/classifier/zero-shot-user-mode/output/instruction/1880332
new file mode 100644
index 000000000..3bfbd35d9
--- /dev/null
+++ b/results/classifier/zero-shot-user-mode/output/instruction/1880332
@@ -0,0 +1,13 @@
+instruction: 0.531
+syscall: 0.246
+runtime: 0.223
+
+
+
+Possible regression in QEMU 5.0.0 after CVE-2020-10702 (segmentation fault)
+
+I've come across a very specific situation, but I'm sure it could be replicated in other cases.
+
+In QEMU 5.0.0 when I use user emulation with a cURL binary for aarch64 and connect to a server using TLS 1.2 and ECDHE-ECDSA-CHACHA20-POLY1305 cypher a segmentation fault occurs.
+
+I attach a Dockerfile that reproduces this crash and the strace output with and without the de0b1bae6461f67243282555475f88b2384a1eb9 commit reverted.
\ No newline at end of file