{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68235 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68235 is a memory corruption 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-68235 and fix it if it is affected.\n\nWhat it is: CVE-2025-68235 is a memory corruption 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-68235 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-68235/ (Markdown: https://insights.sbomify.com/CVE-2025-68235/index.md)","id":"CVE-2025-68235","markdown":"https://insights.sbomify.com/CVE-2025-68235/index.md","name":"CVE-2025-68235","record":{"aliases":["AZL-72460","BELL-CVE-2025-68235","DEBIAN-CVE-2025-68235","GHSA-phf7-78w6-7p26","ROOT-OS-DEBIAN-13-CVE-2025-68235","ROOT-OS-UBUNTU-2404-CVE-2025-68235","UBUNTU-CVE-2025-68235"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A memory leak in the Linux kernel nouveau driver can lead to resource exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nnouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot\n\nnvkm_falcon_fw::boot is allocated, but no one frees it. This causes a\nkmemleak warning.\n\nMake sure this data is deallocated.","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":"nouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot","id":"CVE-2025-68235","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"scsi: ufs: ufs-qcom: Fix UFS OCP issue during UFS power down (PC=3)","id":"CVE-2025-68236"},"packages":[],"prev":{"headline":"io_uring/cmd_net: fix wrong argument types for skb_queue_splice()","id":"CVE-2025-68234"},"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 memory leak in the Linux kernel nouveau driver can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2025-68235/"}