mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: huaweicloud <luogengkun@huaweicloud.com>
Cc: cve@kernel.org, linux-cve-announce@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: CVE-2026-93275: perf/x86/intel/pt: Fix stop/start with no update
Date: Tue, 13 Oct 2026 14:46:13 +0200	[thread overview]
Message-ID: <2026101344-darn-elsewhere-8829@gregkh> (raw)
In-Reply-To: <7cbd5c40-55e4-4db3-8175-aec9516f9ba6@huaweicloud.com>

On Fri, Oct 09, 2026 at 04:52:22PM +0800, huaweicloud wrote:
> Dear Linux Kernel CVE Team,
> 
> I would like to request an update to the affected version for
> CVE-2026-93275.
> 
> Although the patch carries a "Fixes:" tag pointing to commit
> 52ca9ced3f707 ("perf/x86/intel/pt: Add Intel PT PMU driver"), which was
> introduced in v4.1, the commit message itself explicitly notes that
> this buggy code path is only exposed after commit 9734e25fbf5ae ("perf:
> Fix the throttle logic for a group") was merged in v6.16.
> 
> Therefore, kernel versions prior to v6.16 that do not include commit
> 9734e25fbf5ae should be considered safe and unaffected by this CVE.
> Please consider updating the CVE record to avoid widespread false
> positives in older LTS branches.
> 
> Proposed Data Amendment:
> • Vulnerability ID: CVE-2026-93275
> • Current Affected Range: From v4.1 (commit 52ca9ced3f707) up to fixed version
> • Corrected Affected Range: From v6.16 (commit 9734e25fbf5ae) up to fixed version
> 
> Thank you for your time and verification.

I've fixed this up now, thanks.  In the future, you can always just send
a patch that adds an updated .vulnerable file for the specific record
and we will be glad to take that.

thanks,

greg k-h

      reply	other threads:[~2026-10-13 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2026092412-CVE-2026-93275-76ec@gregkh>
2026-10-09  8:52 ` huaweicloud
2026-10-13 12:46   ` 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=2026101344-darn-elsewhere-8829@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luogengkun@huaweicloud.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

all inboxes | Powered by JetHome®