From: Sasha Levin <sashal@kernel.org>
To: Anil Altinay <aaltinay@google.com>
Cc: stable@vger.kernel.org
Subject: Re: CVE-2021-3444
Date: Tue, 29 Jun 2021 18:02:14 -0400 [thread overview]
Message-ID: <YNuYZqgFY5VM0hRr@sashalap> (raw)
In-Reply-To: <CACCxZWMREz1AVchULrWpdvtXYdDXJPNbC3qJicQ-S6UnfTbCUQ@mail.gmail.com>
On Tue, Jun 29, 2021 at 01:06:00PM -0700, Anil Altinay wrote:
>Hi,
>
>I realized that this cve(
>https://www.openwall.com/lists/oss-security/2021/03/23/2 ) is not in
>the 4.19 tree but the commits introduced the vulnerability before
>4.19. Is there any reason that the fix was not cherry-picked to 4.19?
Backport wasn't trivial, and no one seemed to care enough about 4.19.
Feel free to backport the fix and send it out for review.
--
Thanks,
Sasha
next prev parent reply other threads:[~2021-06-29 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 20:06 CVE-2021-3444 Anil Altinay
2021-06-29 22:02 ` Sasha Levin [this message]
2021-06-30 12:51 ` CVE-2021-3444 Salvatore Bonaccorso
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=YNuYZqgFY5VM0hRr@sashalap \
--to=sashal@kernel.org \
--cc=aaltinay@google.com \
--cc=stable@vger.kernel.org \
/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