The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Quanmin Yan <yanquanmin1@huawei.com>
Cc: cve@kernel.org, linux-cve-announce@vger.kernel.org,
	linux-kernel@vger.kernel.org, pedrodemargomes@gmail.com
Subject: Re: CVE-2025-68211: ksm: use range-walk function to jump over holes in scan_get_next_rmap_item
Date: Tue, 6 Jan 2026 15:25:51 +0100	[thread overview]
Message-ID: <2026010609-exclusive-graded-7d86@gregkh> (raw)
In-Reply-To: <02ad8760-0a6c-4a33-88ce-4f6644e1c58a@huawei.com>

On Tue, Jan 06, 2026 at 09:36:29PM +0800, Quanmin Yan wrote:
> Hi gregkh,
> 
> I don't think this should be classified as a CVE because the
> patch primarily addresses a performance issue in a rare scenario.

But in that "rare scenario" it is a system denial of service, making
ksmd deadlocked.  Isn't that a real issue that was fixed here?

thanks,

greg k-h

      reply	other threads:[~2026-01-06 14:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2025121634-CVE-2025-68211-180a@gregkh>
2026-01-06 13:36 ` CVE-2025-68211: ksm: use range-walk function to jump over holes in scan_get_next_rmap_item Quanmin Yan
2026-01-06 14:25   ` 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=2026010609-exclusive-graded-7d86@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pedrodemargomes@gmail.com \
    --cc=yanquanmin1@huawei.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