{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40015 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40015 is a vulnerability in Linux, published on 20 Oct 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-40015 and fix it if it is affected.\n\nWhat it is: CVE-2025-40015 is a vulnerability in Linux, published on 20 Oct 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-40015 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-40015/ (Markdown: https://insights.sbomify.com/CVE-2025-40015/index.md)","id":"CVE-2025-40015","markdown":"https://insights.sbomify.com/CVE-2025-40015/index.md","name":"CVE-2025-40015","record":{"aliases":["BELL-CVE-2025-40015","DEBIAN-CVE-2025-40015","GHSA-6ggw-vcg3-gj6g","UBUNTU-CVE-2025-40015"],"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 null pointer dereference in the STM32 CSI driver can cause a kernel crash, requiring local access to exploit.","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\nmedia: stm32-csi: Fix dereference before NULL check\n\nIn 'stm32_csi_start', 'csidev-\u003es_subdev' is dereferenced directly while\nassigning a value to the 'src_pad'. However the same value is being\nchecked against NULL at a later point of time indicating that there\nare chances that the value can be NULL.\n\nMove the dereference after the NULL check.","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":"media: stm32-csi: Fix dereference before NULL check","id":"CVE-2025-40015","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID","id":"CVE-2025-40016"},"packages":[],"prev":{"headline":"objtool, spi: amd: Fix out-of-bounds stack access in amd_set_spi_freq()","id":"CVE-2025-40014"},"products":["Linux"],"published":"2025-10-20","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 STM32 CSI driver can cause a kernel crash, requiring local access to exploit.","url":"https://insights.sbomify.com/CVE-2025-40015/"}