{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97593 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97593 is a vulnerability in Linux, published on 25 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-97593 and fix it if it is affected.\n\nWhat it is: CVE-2026-97593 is a vulnerability in Linux, published on 25 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-97593 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-97593/ (Markdown: https://insights.sbomify.com/CVE-2026-97593/index.md)","id":"CVE-2026-97593","markdown":"https://insights.sbomify.com/CVE-2026-97593/index.md","name":"CVE-2026-97593","record":{"aliases":["BELL-CVE-2026-97593","DEBIAN-CVE-2026-97593","GHSA-grwc-9m6f-f7hf","UBUNTU-CVE-2026-97593"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A missing NULL check in the s390 IOMMU driver allows local attackers to cause a kernel crash via a NULL pointer dereference.","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\niommu/s390: Fix NULL dereference in iova_to_phys() with ZPCI_TABLE_TYPE_RFX\n\nWhen using a 5-level translation table via ZPCI_TABLE_TYPE_RFX\nget_rso_from_iova() returns NULL when the region-first entry is invalid.\nYet in get_rto_from_iova() the region-second origin rso is not checked\nto be non-NULL before accessing rso[rsx] leading to a NULL pointer\ndereference instead of a NULL return when iova_to_phys() is called on\na unmapped IOVA. Fix this by adding the missing 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":"iommu/s390: Fix NULL dereference in iova_to_phys() with ZPCI_TABLE_TYPE_RFX","id":"CVE-2026-97593","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"landlock: Fix use-after-free of the source's parent directory","id":"CVE-2026-97594"},"packages":[],"prev":{"headline":"s390/crypto: Fix missing scrub of temp buffers with AES ctr and gcm algorithm","id":"CVE-2026-97592"},"products":["Linux"],"published":"2026-09-25","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 missing NULL check in the s390 IOMMU driver allows local attackers to cause a kernel crash via a NULL pointer dereference.","url":"https://insights.sbomify.com/CVE-2026-97593/"}