From: Greg KH <gregkh@linuxfoundation.org>
To: Guruswamy Basavaiah <guruswamy.basavaiah@broadcom.com>
Cc: stable@vger.kernel.org, ajay.kaher@broadcom.com,
tapas.kundu@broadcom.com
Subject: Re: [PATCH 5.10.y 0/3] Backport Fixes to 5.10.y
Date: Fri, 23 Feb 2024 14:07:04 +0100 [thread overview]
Message-ID: <2024022356-renewable-armhole-93da@gregkh> (raw)
In-Reply-To: <20240210201445.3089482-4-guruswamy.basavaiah@broadcom.com>
On Sun, Feb 11, 2024 at 01:44:45AM +0530, Guruswamy Basavaiah wrote:
> Here are the three backported patches aimed at addressing a potential
> crash and an actual crash.
>
> Patch 1 Fix potential OOB access in receive_encrypted_standard() if
> server returned a large shdr->NextCommand in cifs.
>
> Patch 2 fix validate offsets and lengths before dereferencing create
> contexts in smb2_parse_contexts().
>
> Patch 3 fix issue in patch 2.
>
> The original patches were authored by Paulo Alcantara <pc@manguebit.com>.
> Original Patches:
> 1. eec04ea11969 ("smb: client: fix OOB in receive_encrypted_standard()")
> 2. af1689a9b770 ("smb: client: fix potential OOBs in smb2_parse_contexts()")
> 3. 76025cc2285d ("smb: client: fix parsing of SMB3.1.1 POSIX create context")
>
> Please review and consider applying these patches.
All now qeued up, thanks!
greg k-h
prev parent reply other threads:[~2024-02-23 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 20:14 [PATCH 5.10.y 1/3] smb: client: fix OOB in receive_encrypted_standard() Guruswamy Basavaiah
2024-02-10 20:14 ` [PATCH 5.10.y 2/3] smb: client: fix potential OOBs in smb2_parse_contexts() Guruswamy Basavaiah
2024-02-10 20:14 ` [PATCH 5.10.y 3/3] smb: client: fix parsing of SMB3.1.1 POSIX create context Guruswamy Basavaiah
2024-02-10 20:14 ` [PATCH 5.10.y 0/3] Backport Fixes to 5.10.y Guruswamy Basavaiah
2024-02-23 13:07 ` Greg KH [this message]
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=2024022356-renewable-armhole-93da@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ajay.kaher@broadcom.com \
--cc=guruswamy.basavaiah@broadcom.com \
--cc=stable@vger.kernel.org \
--cc=tapas.kundu@broadcom.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