public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Doebel, Bjoern" <doebel@amazon.de>
Cc: stable@vger.kernel.org
Subject: Re: Backport commit fc4992458e0a ("fs/ntfs3: Add null pointer checks")
Date: Wed, 21 Feb 2024 12:04:01 +0100	[thread overview]
Message-ID: <2024022155-kissing-chuck-466f@gregkh> (raw)
In-Reply-To: <67c3ec91-2879-4a6e-9213-b147aaef74ff@amazon.de>

On Tue, Feb 13, 2024 at 02:00:25PM +0100, Doebel, Bjoern wrote:
> Hi,
> 
> please backport commit fc4992458e0a ("fs/ntfs3: Add null pointer checks") to the 5.15 and 6.1 stable branches.
> 
> Commit message
> 
> """
> Added null pointer checks in function ntfs_security_init.
> Also added le32_to_cpu in functions ntfs_security_init and indx_read.
> """
> 
> We are able to reproduce below Syzkaller report on these two stable builds. The issue does not reproduce on upstream, older, or newer LTS releases. Above patch fixes the issue.

Now queued up,t hanks.

greg k-h

      reply	other threads:[~2024-02-21 11:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 13:00 Backport commit fc4992458e0a ("fs/ntfs3: Add null pointer checks") Doebel, Bjoern
2024-02-21 11:04 ` 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=2024022155-kissing-chuck-466f@gregkh \
    --to=greg@kroah.com \
    --cc=doebel@amazon.de \
    --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