{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68238 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68238 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-68238 and fix it if it is affected.\n\nWhat it is: CVE-2025-68238 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-68238 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-68238/ (Markdown: https://insights.sbomify.com/CVE-2025-68238/index.md)","id":"CVE-2025-68238","markdown":"https://insights.sbomify.com/CVE-2025-68238/index.md","name":"CVE-2025-68238","record":{"aliases":["BELL-CVE-2025-68238","DEBIAN-CVE-2025-68238","GHSA-gq5h-xxh9-g765","ROOT-OS-DEBIAN-12-CVE-2025-68238","ROOT-OS-DEBIAN-13-CVE-2025-68238","ROOT-OS-UBUNTU-2204-CVE-2025-68238","ROOT-OS-UBUNTU-2404-CVE-2025-68238","UBUNTU-CVE-2025-68238"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel NAND driver","requires_auth":"none","summary":"A NULL pointer dereference in the Cadence NAND driver can cause a kernel crash, leading to denial of service for local attackers.","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\nmtd: rawnand: cadence: fix DMA device NULL pointer dereference\n\nThe DMA device pointer `dma_dev` was being dereferenced before ensuring\nthat `cdns_ctrl-\u003edmac` is properly initialized.\n\nMove the assignment of `dma_dev` after successfully acquiring the DMA\nchannel to ensure the pointer is valid before use.","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":"mtd: rawnand: cadence: fix DMA device NULL pointer dereference","id":"CVE-2025-68238","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"binfmt_misc: restore write access before closing files opened by open_exec()","id":"CVE-2025-68239"},"packages":[],"prev":{"headline":"mtdchar: fix integer overflow in read/write ioctls","id":"CVE-2025-68237"},"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-23","vendors":["Linux"]},"summary":"A NULL pointer dereference in the Cadence NAND driver can cause a kernel crash, leading to denial of service for local attackers.","url":"https://insights.sbomify.com/CVE-2025-68238/"}