From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] cve: add test reproducer for cve-2025-21756
Date: Tue, 23 Sep 2025 10:03:47 +0200 [thread overview]
Message-ID: <aNJUYxkKPS2rLfVx@yuki.lan> (raw)
In-Reply-To: <4721ff31-7d9f-42a2-8217-6d1d4006f661@suse.com>
Hi!
> I guess we need to verify that, if system is not crashed, we should
> check kernel messages in order to find any error. Is there a smart way
> to do it? I could parse data via FILE_LINES_SCANF() macro, but that
> would require multiple iterations. The alternative is just to parse the
> entire /dev/kmsg via read() and to find:
>
> 1. use-after-free message
> 2. test name after it
> 3. failing syscall vsock_release
>
> WDYT? Maybe there are better ways to do it.
We have library functions to watch for kernel taint flags, that should
be enough to detect this.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2025-09-23 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 10:18 [LTP] [PATCH] cve: add test reproducer for cve-2025-21756 Andrea Cervesato
2025-09-22 14:32 ` Cyril Hrubis
2025-09-23 7:56 ` Andrea Cervesato via ltp
2025-09-23 8:03 ` Cyril Hrubis [this message]
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=aNJUYxkKPS2rLfVx@yuki.lan \
--to=chrubis@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox