{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68177 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68177 is a vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68177 and fix it if it is affected.\n\nWhat it is: CVE-2025-68177 is a vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-68177 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-68177/ (Markdown: https://insights.sbomify.com/CVE-2025-68177/index.md)","id":"CVE-2025-68177","markdown":"https://insights.sbomify.com/CVE-2025-68177/index.md","name":"CVE-2025-68177","record":{"aliases":["BELL-CVE-2025-68177","DEBIAN-CVE-2025-68177","GHSA-q4w5-8ph4-32c6","ROOT-OS-DEBIAN-12-CVE-2025-68177","ROOT-OS-DEBIAN-13-CVE-2025-68177","ROOT-OS-UBUNTU-2204-CVE-2025-68177","ROOT-OS-UBUNTU-2404-CVE-2025-68177","UBUNTU-CVE-2025-68177"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A NULL pointer dereference in the Linux kernel cpufreq longhaul driver can cause a system crash or panic, requiring a kernel patch.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq/longhaul: handle NULL policy in longhaul_exit\n\nlonghaul_exit() was calling cpufreq_cpu_get(0) without checking\nfor a NULL policy pointer. On some systems, this could lead to a\nNULL dereference and a kernel warning or panic.\n\nThis patch adds a check using unlikely() and returns early if the\npolicy is NULL.\n\nBugzilla: #219962","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"cpufreq/longhaul: handle NULL policy in longhaul_exit","id":"CVE-2025-68177","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":8,"next":{"headline":"blk-cgroup: fix possible deadlock while configuring policy","id":"CVE-2025-68178"},"packages":[],"prev":{"headline":"PCI: cadence: Check for the existence of cdns_pcie::ops before using it","id":"CVE-2025-68176"},"products":["Linux"],"published":"2025-12-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A NULL pointer dereference in the Linux kernel cpufreq longhaul driver can cause a system crash or panic, requiring a kernel patch.","url":"https://insights.sbomify.com/CVE-2025-68177/"}