From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH 2/2] cve/sctphantom: Add reproducer for CVE-2026-64564
Date: Mon, 10 Aug 2026 20:06:20 +0200 [thread overview]
Message-ID: <20260810180620.GF1049677@pevik> (raw)
In-Reply-To: <20260810-sctphantom-v1-2-f8e9ee72a648@suse.com>
Hi Andrea,
> Add a reproducer for CVE-2026-64564, a use-after-free in the SCTP
> Dynamic Address Reconfiguration (RFC 5061) DEL-IP processing.
> This vulnerability was fixed upstream by commit 9b2854f86f0b ("sctp:
> don't free the ASCONF's own transport in DEL-IP processing").
> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> Link: https://matrix.tencent.com/en/2026/08/06/sctphantom-CVE-2026-64564
Nice reproducer, full of magic. Generally LGTM, few notes bellow?
Acked-by: Petr Vorel <pvorel@suse.cz>
Tested-by: Petr Vorel <pvorel@suse.cz>
> +static void setup(void)
> +{
> + int fd;
> + const struct tst_path_val sysctls[] = {
> + {"/proc/sys/net/sctp/addip_enable", "1", TST_SR_TCONF},
> + {"/proc/sys/net/sctp/addip_noauth_enable", "1", TST_SR_TCONF},
> + {}
> + };
Can't this be part of .save_restore in struct tst_test?
> + const struct tst_path_val *sysctl;
> +
> + tst_modprobe("sctp", NULL);
...
> +
> +/*
> + * The freed transport is released by an RCU callback; once it is gone,
> + * reading the association status dereferences the stale primary_path,
> + * which KASAN reports as a use-after-free.
> + */
> +static void probe_uaf(void)
> +{
> + uint8_t buf[512];
> + long delay = 1;
> + int i;
> +
> + tst_res(TINFO, "probing the stale primary path via SCTP_STATUS");
> +
> + for (i = 0; i < 12; i++) {
> + socklen_t len = sizeof(buf);
> +
> + TEST(getsockopt(cli_fd, SOL_SCTP, SCTP_STATUS, buf, &len));
What is the point of using TEST() macro here. Why not run getsockopt() directly?
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-08-10 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 16:28 [LTP] [PATCH 0/2] Add reproducer for sctphantom CVE Andrea Cervesato
2026-08-10 16:28 ` [LTP] [PATCH 1/2] sctp: add lapi fallback definitions Andrea Cervesato
2026-08-10 16:57 ` [LTP] " linuxtestproject.agent
2026-08-10 17:39 ` [LTP] [PATCH 1/2] " Petr Vorel
2026-08-10 16:28 ` [LTP] [PATCH 2/2] cve/sctphantom: Add reproducer for CVE-2026-64564 Andrea Cervesato
2026-08-10 18:06 ` Petr Vorel [this message]
2026-08-10 18:14 ` Andrea Cervesato via ltp
2026-08-11 5:35 ` 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=20260810180620.GF1049677@pevik \
--to=pvorel@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