Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Alexey Panov <apanov@astralinux.ru>,
	stable@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Gao Xiang <xiang@kernel.org>, Chao Yu <chao@kernel.org>,
	Yue Hu <huyue2@coolpad.com>,
	Jeffle Xu <jefflexu@linux.alibaba.com>,
	linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	lvc-project@linuxtesting.org,
	Max Kellermann <max.kellermann@ionos.com>
Subject: Re: [PATCH 6.1 0/2] erofs: handle overlapped pclusters out of crafted images properly
Date: Sat, 1 Mar 2025 10:52:30 +0800	[thread overview]
Message-ID: <c9cf602f-de40-4917-9f8a-d6b88e57482d@linux.alibaba.com> (raw)
In-Reply-To: <20250228165103.26775-1-apanov@astralinux.ru>



On 2025/3/1 00:51, Alexey Panov wrote:
> Commit 9e2f9d34dd12 ("erofs: handle overlapped pclusters out of crafted
> images properly") fixes CVE-2024-47736 [1] but brings another problem [2].
> So commit 1a2180f6859c ("erofs: fix PSI memstall accounting") should be
> backported too.
> 
> [1] https://nvd.nist.gov/vuln/detail/CVE-2024-47736
> [2] https://lore.kernel.org/all/CAKPOu+8tvSowiJADW2RuKyofL_CSkm_SuyZA7ME5vMLWmL6pqw@mail.gmail.com/
> 

Thanks for your effort! Patches look good to me.

Thanks,
Gao Xiang

      parent reply	other threads:[~2025-03-01  2:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 16:51 [PATCH 6.1 0/2] erofs: handle overlapped pclusters out of crafted images properly Alexey Panov
2025-02-28 16:51 ` [PATCH 6.1 1/2] " Alexey Panov
2025-03-01  4:21   ` Sasha Levin
2025-03-02 10:56   ` Fedor Pchelkin
2025-03-02 17:41     ` Gao Xiang
2025-03-02 17:56       ` Gao Xiang
2025-03-02 18:13       ` Fedor Pchelkin
2025-03-03  0:31         ` Gao Xiang
2025-03-03  9:19           ` Fedor Pchelkin
2025-03-04 11:18             ` Алексей Панов
2025-02-28 16:51 ` [PATCH 6.1 2/2] erofs: fix PSI memstall accounting Alexey Panov
2025-03-01  4:20   ` Sasha Levin
2025-03-01  2:52 ` Gao Xiang [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=c9cf602f-de40-4917-9f8a-d6b88e57482d@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=apanov@astralinux.ru \
    --cc=chao@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=huyue2@coolpad.com \
    --cc=jefflexu@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=max.kellermann@ionos.com \
    --cc=stable@vger.kernel.org \
    --cc=xiang@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