mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: cve@kernel.org, linux-kernel@vger.kernel.org,
	linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: CVE-2023-53027: erofs: fix kvcalloc() misuse with __GFP_NOFAIL
Date: Fri, 28 Mar 2025 14:43:04 +0800	[thread overview]
Message-ID: <7e5c7a5e-8853-4a9d-983d-b51cb416e078@linux.alibaba.com> (raw)
In-Reply-To: <2025032719-CVE-2023-53027-dc56@gregkh>

Hi,

On 2025/3/28 00:44, Greg Kroah-Hartman wrote:
> Description
> ===========
> 
> In the Linux kernel, the following vulnerability has been resolved:
> 
> erofs: fix kvcalloc() misuse with __GFP_NOFAIL
> 
> As reported by syzbot [1], kvcalloc() cannot work with  __GFP_NOFAIL.
> Let's use kcalloc() instead.
> 
> [1] https://lore.kernel.org/r/0000000000007796bd05f1852ec2@google.com
> 
> The Linux kernel CVE team has assigned CVE-2023-53027 to this issue.

I think this CVE is invalid since it was then reverted by
upstream commit 647dd2c3f0e1 ("erofs: Revert "erofs: fix kvcalloc()
misuse with __GFP_NOFAIL"")

since it's not the correct way to fix this.

The original issue was fixed by
commit e9c3cda4d86e ("mm, vmalloc: fix high order __GFP_NOFAIL
allocations") instead.

Thanks,
Gao Xiang

       reply	other threads:[~2025-03-28  6:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2025032719-CVE-2023-53027-dc56@gregkh>
2025-03-28  6:43 ` Gao Xiang [this message]
2025-03-28  6:53   ` Greg Kroah-Hartman
2025-03-28  6:55     ` Gao Xiang

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=7e5c7a5e-8853-4a9d-983d-b51cb416e078@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=cve@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®