Re: CVE-2026-93275: perf/x86/intel/pt: Fix stop/start with no update

Re: CVE-2026-93275: perf/x86/intel/pt: Fix stop/start with no update

[huaweicloud]

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.

Best regards,

Gengkun

Re: CVE-2026-93275: perf/x86/intel/pt: Fix stop/start with no update

[Greg KH]

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