Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: kuba@kernel.org, stable@vger.kernel.org, davem@davemloft.net,
	horms@kernel.org, lee@kernel.org, sashal@kernel.org,
	sd@queasysnail.net, sec@valis.email, liam.merwick@oracle.com,
	vegard.nossum@oracle.com, dan.carpenter@linaro.org
Subject: Re: [PATCH 5.15.y] tls: fix race between tx work scheduling and socket close
Date: Tue, 13 Aug 2024 12:39:00 +0200	[thread overview]
Message-ID: <2024081352-reiterate-decoy-30b2@gregkh> (raw)
In-Reply-To: <20240802113931.2501476-1-harshit.m.mogalapalli@oracle.com>

On Fri, Aug 02, 2024 at 04:39:31AM -0700, Harshit Mogalapalli wrote:
> From: Jakub Kicinski <kuba@kernel.org>
> 
> commit e01e3934a1b2d122919f73bc6ddbe1cdafc4bbdb upstream.
> 
> Similarly to previous commit, the submitting thread (recvmsg/sendmsg)
> may exit as soon as the async crypto handler calls complete().
> Reorder scheduling the work before calling complete().
> This seems more logical in the first place, as it's
> the inverse order of what the submitting thread will do.
> 
> Reported-by: valis <sec@valis.email>
> Fixes: a42055e8d2c3 ("net/tls: Add support for async encryption of records for performance")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> Reviewed-by: Simon Horman <horms@kernel.org>
> Reviewed-by: Sabrina Dubroca <sd@queasysnail.net>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> [Lee: Fixed merge-conflict in Stable branches linux-6.1.y and older]
> Signed-off-by: Lee Jones <lee@kernel.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> [Harshit: bp to 5.15.y, minor conflict resolutin due to missing commit:
> 8ae187386420 ("tls: Only use data field in crypto completion function")
> in 5.15.y]
> Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
> ---
> This is a fix for CVE-2024-26585, minor conflict resolution involved
> Ran the tls self tests: 
> 
> ok 183 tls.13_chacha.shutdown_reuse
> # PASSED: 183 / 183 tests passed.
> # Totals: pass:183 fail:0 xfail:0 xpass:0 skip:0 error:0
> 
>  net/tls/tls_sw.c | 16 ++++++----------
>  1 file changed, 6 insertions(+), 10 deletions(-)

Now queued up, thanks.

greg k-h

  reply	other threads:[~2024-08-13 10:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 15:59 [PATCH 6.1 1/1] tls: fix race between tx work scheduling and socket close Lee Jones
2024-03-07 17:08 ` Jakub Kicinski
2024-03-07 17:09   ` Lee Jones
2024-03-07 17:14     ` Jakub Kicinski
2024-08-02 11:39       ` [PATCH 5.15.y] " Harshit Mogalapalli
2024-08-13 10:39         ` Greg Kroah-Hartman [this message]
2024-08-02 11:35   ` [PATCH 6.1 1/1] " Harshit Mogalapalli
2024-03-27 14:35 ` Greg KH
2024-03-27 14:42   ` Lee Jones

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=2024081352-reiterate-decoy-30b2@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@linaro.org \
    --cc=davem@davemloft.net \
    --cc=harshit.m.mogalapalli@oracle.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=lee@kernel.org \
    --cc=liam.merwick@oracle.com \
    --cc=sashal@kernel.org \
    --cc=sd@queasysnail.net \
    --cc=sec@valis.email \
    --cc=stable@vger.kernel.org \
    --cc=vegard.nossum@oracle.com \
    /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