From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: Cyril Hrubis <chrubis@suse.cz>, Martin Doucha <mdoucha@suse.cz>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [COMMITTED] runtest/cve: Fix wrong cve tag
Date: Wed, 8 Sep 2021 07:22:50 +0000 [thread overview]
Message-ID: <613864D4.5030400@fujitsu.com> (raw)
Message-ID: <20210908072250.KtLy-PY-EmHNR1xE-kCdkR72yjLSeg8NbGZ8d8h9GTM@z> (raw)
In-Reply-To: <1630897958-2160-1-git-send-email-xuyang2018.jy@fujitsu.com>
Hi Cyril, Martin
In fact, Look the following url:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3609
It said nothing and seems this cve number doesn't exist.
Do you know what happen?
Best Regards
Yang Xu
> can_bcm01 is designed to test cve-2021-3609 instead of cve-2021-6309.
>
> Fixes: 027ea6171c40 ("Add test for CVE 2021-3609")
> Signed-off-by: Yang Xu<xuyang2018.jy@fujitsu.com>
> ---
> runtest/cve | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/runtest/cve b/runtest/cve
> index 357b88feb..01211b5aa 100644
> --- a/runtest/cve
> +++ b/runtest/cve
> @@ -67,7 +67,7 @@ cve-2020-14416 pty03
> cve-2020-25705 icmp_rate_limit01
> cve-2020-29373 io_uring02
> cve-2021-3444 bpf_prog05
> -cve-2021-6309 can_bcm01
> +cve-2021-3609 can_bcm01
> cve-2021-22555 setsockopt08 -i 100
> cve-2021-26708 vsock01
> # Tests below may cause kernel memory leak
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-09-08 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 3:12 [LTP] [COMMITTED] runtest/cve: Fix wrong cve tag Yang Xu
2021-09-06 3:12 ` Yang Xu
2021-09-08 7:22 ` xuyang2018.jy [this message]
2021-09-08 7:22 ` xuyang2018.jy
2021-09-08 8:49 ` Martin Doucha
2021-09-08 8:49 ` Martin Doucha
2021-09-08 10:44 ` Cyril Hrubis
2021-09-08 10:44 ` 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=613864D4.5030400@fujitsu.com \
--to=xuyang2018.jy@fujitsu.com \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/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.