{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90405 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90405 is a vulnerability in Linux, published on 17 Sep 2026. 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-2026-90405 and fix it if it is affected.\n\nWhat it is: CVE-2026-90405 is a vulnerability in Linux, published on 17 Sep 2026. 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-2026-90405 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-2026-90405/ (Markdown: https://insights.sbomify.com/CVE-2026-90405/index.md)","id":"CVE-2026-90405","markdown":"https://insights.sbomify.com/CVE-2026-90405/index.md","name":"CVE-2026-90405","record":{"aliases":["DEBIAN-CVE-2026-90405","GHSA-8r39-p738-wgfm","UBUNTU-CVE-2026-90405"],"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 DCMI driver probe function can cause a kernel crash, leading to denial of service.","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: dcmi: fix some error handling bugs in probe()\n\nThere are a few issues here:\n\n1) After we assign:\n        chan = dma_request_chan(\u0026pdev-\u003edev, \"tx\");\n   Then the error paths need to clean up before returning.  The first\n   error path does a direct return.\n2) The error paths check \"dcmi-\u003emdma_chan\" but that is not assigned\n   until later so it results in memory leaks.  Test \"mdma_chan\"\n   instead.\n3) The error handling calls dma_release_channel(dcmi-\u003edma_chan) before\n   \"dcmi-\u003edma_chan\" has been assigned which leads to a NULL pointer\n   dereference.  Use the \"chan\" variable instead.\n\nI also moved the call to dma_release_channel() after the call to\ndma_release_channel() so it mirrors the allocation code better.","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: dcmi: fix some error handling bugs in probe()","id":"CVE-2026-90405","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"media: qcom: iris: handle runtime PM resume failure in core deinit","id":"CVE-2026-90406"},"packages":[],"prev":{"headline":"platform/chrome: cros_ec_debugfs: Unregister panic notifier","id":"CVE-2026-90404"},"products":["Linux"],"published":"2026-09-17","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-10-19","vendors":["Linux"]},"summary":"A null pointer dereference in the STM32 DCMI driver probe function can cause a kernel crash, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-90405/"}