CVE-2025-68177
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-16

Last updated on: 2025-12-18

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: cpufreq/longhaul: handle NULL policy in longhaul_exit longhaul_exit() was calling cpufreq_cpu_get(0) without checking for a NULL policy pointer. On some systems, this could lead to a NULL dereference and a kernel warning or panic. This patch adds a check using unlikely() and returns early if the policy is NULL. Bugzilla: #219962
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-16
Last Modified
2025-12-18
Generated
2026-05-27
AI Q&A
2025-12-16
EPSS Evaluated
2026-05-25
NVD
CVE-2025-68177
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?

Apply the patch that adds a NULL check in longhaul_exit() to prevent the NULL dereference. This involves updating the Linux kernel to the fixed version that includes this patch.


Can you explain this vulnerability to me?

This vulnerability occurs in the Linux kernel's cpufreq/longhaul component where the function longhaul_exit() calls cpufreq_cpu_get(0) without checking if the policy pointer is NULL. On some systems, this can cause a NULL pointer dereference, leading to a kernel warning or panic. The issue is fixed by adding a check to return early if the policy is NULL.


How can this vulnerability impact me? :

If triggered, this vulnerability can cause a kernel warning or panic due to a NULL pointer dereference. This can lead to system instability or crashes, potentially causing downtime or loss of service.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart