Kernel panic via unchecked CPU policy pointer
Published Dec 16, 2025 · Updated Dec 16, 2025
NULL-pointer dereference in the Linux kernel allows local users to panic affected systems through the longhaul CPU-frequency driver. The longhaul_exit() teardown path calls cpufreq_cpu_get(0) and dereferences the returned policy without first checking whether it is NULL. Exploitation requires local high privileges and a system using the legacy longhaul driver; the bounded consequence is a kernel warning or panic.
Summary
What happened
NULL-pointer dereference in the Linux kernel allows local users to panic affected systems through the longhaul CPU-frequency driver. The longhaul_exit() teardown path calls cpufreq_cpu_get(0) and dereferences the returned policy without first checking whether it is NULL. Exploitation requires local high privileges and a system using the legacy longhaul driver; the bounded consequence is a kernel warning or panic.
The record
- CVE
- CVE-2025-68177
- Published
- Dec 16, 2025
- Updated
- Dec 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 16, 2025CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <55cf586b9556863e3c2a45460aba71bcb2be5bcd
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <592532a77b736b5153e0c2e4c74aa50af0a352ab
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <64adabb6d9d51b7e7c02fe733346a2c4dd738488
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <809cf2a7794ca4c14c304b349f4c3ae220701ce4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8d6791c480f22d6e9a566eaa77336d3d37c5c591
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <956b56d17a89775e4957bbddefa45cd3c6c71000
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b02352dd2e6cca98777714cc2a27553191df70db
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fd93e1d71b3b14443092919be12b1abf08de35eb
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo