CVE-2025-39799

View on CVE.org
Published Sep 12, 2025 CVSS n/a EPSS n/a KEV · Not listed
Description
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

Analysis

This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

Remediation

No remediation available yet

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2025-29055 This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
References

No reference.

History
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ACPI: processor: perflib: Move problematic pr->performance check Commit d33bd88ac0eb ("ACPI: processor: perflib: Fix initial _PPC limit application") added a pr->performance check that prevents the frequency QoS request from being added when the given processor has no performance object. Unfortunately, this causes a WARN() in freq_qos_remove_request() to trigger on an attempt to take the given CPU offline later because the frequency QoS object has not been added for it due to the missing performance object. Address this by moving the pr->performance check before calling acpi_processor_get_platform_limit() so it only prevents a limit from being set for the CPU if the performance object is not present. This way, the frequency QoS request is added as it was before the above commit and it is present all the time along with the CPU's cpufreq policy regardless of whether or not the CPU is online. This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Title ACPI: processor: perflib: Move problematic pr->performance check
Type Values Removed Values Added
First Time appeared Linux
Linux linux Kernel
Vendors & Products Linux
Linux linux Kernel
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ACPI: processor: perflib: Move problematic pr->performance check Commit d33bd88ac0eb ("ACPI: processor: perflib: Fix initial _PPC limit application") added a pr->performance check that prevents the frequency QoS request from being added when the given processor has no performance object. Unfortunately, this causes a WARN() in freq_qos_remove_request() to trigger on an attempt to take the given CPU offline later because the frequency QoS object has not been added for it due to the missing performance object. Address this by moving the pr->performance check before calling acpi_processor_get_platform_limit() so it only prevents a limit from being set for the CPU if the performance object is not present. This way, the frequency QoS request is added as it was before the above commit and it is present all the time along with the CPU's cpufreq policy regardless of whether or not the CPU is online.
Title ACPI: processor: perflib: Move problematic pr->performance check
References
Weaknesses

No weakness.

Sources

Status
REJECTED
Assigner
Linux
Published
Updated
Sep 29, 2025, 6:10 AM
Reserved
Apr 16, 2025, 7:20 AM

View source JSON

No data.

Status
Rejected
Published
Sep 12, 2025, 4:15 PM
Modified
Oct 16, 2026, 2:10 PM

View source JSON

No data.

No data.