CVE-2025-68177
Published Dec 16, 2025
Modified Apr 15, 2026
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
Is your site exposed to CVE-2025-68177?
Run a free security scan — no signup, results in seconds.
References
Other References
https://git.kernel.org/stable/c/55cf586b9556863e3c2a45460aba71bcb2be5bcd
https://git.kernel.org/stable/c/592532a77b736b5153e0c2e4c74aa50af0a352ab
https://git.kernel.org/stable/c/64adabb6d9d51b7e7c02fe733346a2c4dd738488
https://git.kernel.org/stable/c/809cf2a7794ca4c14c304b349f4c3ae220701ce4
https://git.kernel.org/stable/c/8d6791c480f22d6e9a566eaa77336d3d37c5c591
https://git.kernel.org/stable/c/956b56d17a89775e4957bbddefa45cd3c6c71000
https://git.kernel.org/stable/c/b02352dd2e6cca98777714cc2a27553191df70db
https://git.kernel.org/stable/c/fd93e1d71b3b14443092919be12b1abf08de35eb
Frequently Asked Questions
What is CVE-2025-68177? +
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
How do I check if I'm vulnerable to CVE-2025-68177? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.