From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] cve: add CVE-2025-38236 test
Date: Tue, 12 Aug 2025 13:09:04 +0200 [thread overview]
Message-ID: <20250812110904.GC835467@pevik> (raw)
In-Reply-To: <d6ff8f3c-6ac6-4bd5-beac-036b775698ec@suse.com>
Hi Andrea, Wei,
...
> > 1) I suggest check dummy value after each SAFE_RECV above also
> This is not useful because bug is triggered after the second send()
> > 2) Better send different char for different sent such as A,B,C
+1, very good point. While the original C reproducer from Jann Horn in chromium
[1] used the same char "A", the pythonized reproducer from the kernel fix author
Kuniyuki Iwashima used a different chars. Obviously debugging the fix it was
easier with different chars :).
Kind regards,
Petr
[1] https://project-zero.issues.chromium.org/issues/423023990
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=32ca245464e1
> This can be done
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-08-12 11:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 8:45 [LTP] [PATCH] cve: add CVE-2025-38236 test Andrea Cervesato
2025-08-12 9:43 ` Wei Gao via ltp
2025-08-12 10:57 ` Andrea Cervesato via ltp
2025-08-12 11:09 ` Petr Vorel [this message]
2025-08-12 10:12 ` Petr Vorel
2025-08-12 11:09 ` Cyril Hrubis
2025-08-12 11:45 ` [LTP] [doc, runtest] [was: Re: [PATCH] cve: add CVE-2025-38236 test] Petr Vorel
2025-08-12 12:09 ` Cyril Hrubis
2025-08-18 6:08 ` Petr Vorel
2025-08-12 10:51 ` [LTP] [PATCH] cve: add CVE-2025-38236 test Petr Vorel
2025-08-12 10:55 ` Andrea Cervesato via ltp
2025-08-12 11:14 ` Cyril Hrubis
2025-08-12 11:17 ` Andrea Cervesato via ltp
2025-08-12 11:50 ` Petr Vorel
2025-08-12 11:25 ` Petr Vorel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250812110904.GC835467@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.