CVE-2025-68177: cpufreq/longhaul: handle NULL policy in longhaul_exit
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 55cf586b9556863e3c2a45460aba71bcb2be5bcd, 592532a77b736b5153e0c2e4c74aa50af0a352ab, 64adabb6d9d51b7e7c02fe733346a2c4dd738488.
Low priority for now. Upgrade to Linux Linux 55cf586b9556863e3c2a45460aba71bcb2be5bcd, 592532a77b736b5153e0c2e4c74aa50af0a352ab, 64adabb6d9d51b7e7c02fe733346a2c4dd738488 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Published
- Dec 16, 2025
- Updated
- Oct 14, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.10affected
- b43a7ffbf33be7e4d3b10b7714ee663ea2c52fe2 and later · before b02352dd2e6cca98777714cc2a27553191df70dbaffected · git
- b43a7ffbf33be7e4d3b10b7714ee663ea2c52fe2 and later · before 956b56d17a89775e4957bbddefa45cd3c6c71000affected · git
- b43a7ffbf33be7e4d3b10b7714ee663ea2c52fe2 and later · before 55cf586b9556863e3c2a45460aba71bcb2be5bcdaffected · git
- b43a7ffbf33be7e4d3b10b7714ee663ea2c52fe2 and later · before fd93e1d71b3b14443092919be12b1abf08de35ebaffected · git
- b43a7ffbf33be7e4d3b10b7714ee663ea2c52fe2 and later · before 8d6791c480f22d6e9a566eaa77336d3d37c5c591affected · git
- b43a7ffbf33be7e4d3b10b7714ee663ea2c52fe2 and later · before 64adabb6d9d51b7e7c02fe733346a2c4dd738488affected · git
- b43a7ffbf33be7e4d3b10b7714ee663ea2c52fe2 and later · before 809cf2a7794ca4c14c304b349f4c3ae220701ce4affected · git
- b43a7ffbf33be7e4d3b10b7714ee663ea2c52fe2 and later · before 592532a77b736b5153e0c2e4c74aa50af0a352abaffected · git
- before 3.10not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.159-1 | 6.1.159-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.8-1 | 6.17.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68175Dec 16, 2025 · media: nxp: imx8-isi: Fix streaming cleanup on release31Monitor
- ← EarlierCVE-2025-68176Dec 16, 2025 · PCI: cadence: Check for the existence of cdns_pcie::ops before using it0Monitor
- Later →CVE-2025-68178Dec 16, 2025 · blk-cgroup: fix possible deadlock while configuring policy0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 55cf586b9556863e3c2a45460aba71bcb2be5bcd | Vendor (CNA) |
| Linux Linux | 592532a77b736b5153e0c2e4c74aa50af0a352ab | Vendor (CNA) |
| Linux Linux | 64adabb6d9d51b7e7c02fe733346a2c4dd738488 | Vendor (CNA) |
| Linux Linux | 809cf2a7794ca4c14c304b349f4c3ae220701ce4 | Vendor (CNA) |
| Linux Linux | 8d6791c480f22d6e9a566eaa77336d3d37c5c591 | Vendor (CNA) |
| Linux Linux | 956b56d17a89775e4957bbddefa45cd3c6c71000 | Vendor (CNA) |
| Linux Linux | b02352dd2e6cca98777714cc2a27553191df70db | Vendor (CNA) |
| Linux Linux | fd93e1d71b3b14443092919be12b1abf08de35eb | Vendor (CNA) |
| debian:linux | 6.1.159-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/592532a77b736b5153e0c2e4c74aa50af0a352ab
- git.kernel.org/stable/c/64adabb6d9d51b7e7c02fe733346a2c4dd738488
- git.kernel.org/stable/c/809cf2a7794ca4c14c304b349f4c3ae220701ce4
- git.kernel.org/stable/c/8d6791c480f22d6e9a566eaa77336d3d37c5c591
- git.kernel.org/stable/c/956b56d17a89775e4957bbddefa45cd3c6c71000
- git.kernel.org/stable/c/b02352dd2e6cca98777714cc2a27553191df70db
- git.kernel.org/stable/c/fd93e1d71b3b14443092919be12b1abf08de35eb
Vendor advisories and official records. Exploit/PoC links are deliberately left out.