{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90238 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90238 is a denial of service 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-90238 and fix it if it is affected.\n\nWhat it is: CVE-2026-90238 is a denial of service 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-90238 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-90238/ (Markdown: https://insights.sbomify.com/CVE-2026-90238/index.md)","id":"CVE-2026-90238","markdown":"https://insights.sbomify.com/CVE-2026-90238/index.md","name":"CVE-2026-90238","record":{"aliases":["GHSA-gwc7-3f3j-839g","UBUNTU-CVE-2026-90238"],"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 self-deadlock in the AMD ISP4 driver error path causes a system hang when initialization fails, requiring a kernel patch.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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: amd: isp4: fix self-deadlock in isp4sd_pwron_and_init() error path\n\nisp4sd_pwron_and_init() holds ops_mutex via guard(mutex) and, on any\ninit failure, jumps to err_deinit and calls isp4sd_pwroff_and_deinit().\nThat helper takes the same ops_mutex, re-acquiring a non-recursive mutex\nalready held by the current thread, so any init failure deadlocks.\n\nUnwind the error path in stages instead, releasing only what each\nfailure point acquired. This also avoids the issues that an\nunconditional teardown would hit at the earlier failures, such as a\nruntime-PM underflow from pm_runtime_resume_and_get() and MMIO access\nwhile the device is unpowered.","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: amd: isp4: fix self-deadlock in isp4sd_pwron_and_init() error path","id":"CVE-2026-90238","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"media: amd: isp4: release partial allocations in isp4if_alloc_fw_gpumem()","id":"CVE-2026-90239"},"packages":[],"prev":{"headline":"netfilter: nft_ct: move custom expectation support to helper","id":"CVE-2026-90237"},"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 self-deadlock in the AMD ISP4 driver error path causes a system hang when initialization fails, requiring a kernel patch.","url":"https://insights.sbomify.com/CVE-2026-90238/"}