{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68377 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68377 is a vulnerability in Linux, published on 24 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-68377 and fix it if it is affected.\n\nWhat it is: CVE-2025-68377 is a vulnerability in Linux, published on 24 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-68377 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-68377/ (Markdown: https://insights.sbomify.com/CVE-2025-68377/index.md)","id":"CVE-2025-68377","markdown":"https://insights.sbomify.com/CVE-2025-68377/index.md","name":"CVE-2025-68377","record":{"aliases":["BELL-CVE-2025-68377","GHSA-v9c3-fv62-pqcc","UBUNTU-CVE-2025-68377"],"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 missing initialization in Linux kernel namespaces can lead to a null pointer dereference, causing a system crash.","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\nns: initialize ns_list_node for initial namespaces\n\nMake sure that the list is always initialized for initial namespaces.","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":"ns: initialize ns_list_node for initial namespaces","id":"CVE-2025-68377","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"bpf: Fix stackmap overflow check in __bpf_get_stackid()","id":"CVE-2025-68378"},"packages":[],"prev":{"headline":"coresight: ETR: Fix ETR buffer use-after-free issue","id":"CVE-2025-68376"},"products":["Linux"],"published":"2025-12-24","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 missing initialization in Linux kernel namespaces can lead to a null pointer dereference, causing a system crash.","url":"https://insights.sbomify.com/CVE-2025-68377/"}