From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] cve: add test reproducer for cve-2025-21756
Date: Mon, 22 Sep 2025 16:32:13 +0200 [thread overview]
Message-ID: <aNFd7UYkgVk3xgU_@yuki.lan> (raw)
In-Reply-To: <20250922-cve-2025-21756-v1-1-074da211288a@suse.com>
Hi!
> +/*\
> + * Test for CVE-2025-21756 fixed in kernel v6.14:
> + * fcdd2242c023 vsock: Keep the binding until socket destruction
> + *
> + * Reproducer based on:
> + * https://lore.kernel.org/all/20250128-vsock-transport-vs-autobind-v3-5-1cf57065b770@rbox.co/
> + *
> + * Beware, this test will crash the system.
> + */
> +
> +#include "tst_test.h"
> +
> +#if HAVE_LINUX_VM_SOCKETS_H
> +
> +#include "lapi/vm_sockets.h"
Do we need the #if HAVE_LINUX_VM_SOCKETS_H if we include lapi/ fallback?
> +#define MAX_PORT_RETRIES 24
> +#define VMADDR_CID_NONEXISTING 42
> +
> +static int vsock_bind(unsigned int cid, unsigned int port, int type)
> +{
> + int sock;
> +
> + struct sockaddr_vm sa = {
> + .svm_family = AF_VSOCK,
> + .svm_cid = cid,
> + .svm_port = port,
> + };
> +
> + sock = SAFE_SOCKET(AF_VSOCK, type, 0);
> + SAFE_BIND(sock, (struct sockaddr *)&sa, sizeof(sa));
I guess that with the lapi fallback we should TCONF here on ENOSYS
instead and drop the #if at the top.
Other than that the rest looks good.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-09-22 14:31 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 [this message]
2025-09-23 7:56 ` Andrea Cervesato via ltp
2025-09-23 8:03 ` Cyril Hrubis
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=aNFd7UYkgVk3xgU_@yuki.lan \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.de \
--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