{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93133 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93133 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-93133 and fix it if it is affected.\n\nWhat it is: CVE-2026-93133 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-93133 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-93133/ (Markdown: https://insights.sbomify.com/CVE-2026-93133/index.md)","id":"CVE-2026-93133","markdown":"https://insights.sbomify.com/CVE-2026-93133/index.md","name":"CVE-2026-93133","record":{"aliases":["BELL-CVE-2026-93133","DEBIAN-CVE-2026-93133","GHSA-6x8h-vjg9-qvc5","UBUNTU-CVE-2026-93133"],"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":"none","summary":"A missing status check in the Linux kernel's RISC-V ACPI code can lead to a null pointer dereference, causing a system crash.","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\nACPI: RISC-V: Check acpi_get_handle() status in riscv_acpi_add_prt_dep()\n\nIn riscv_acpi_add_prt_dep(), the acpi_get_handle() call can fail which\nwould leave link_handle uninitialized.\n\nFix it by checking the acpi_get_handle() return status and skip the entry\nif it fails.","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":"ACPI: RISC-V: Check acpi_get_handle() status in riscv_acpi_add_prt_dep()","id":"CVE-2026-93133","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"printk: Fix possible console use-after-free","id":"CVE-2026-93134"},"packages":[],"prev":{"headline":"ACPI: RISC-V: Fix riscv_acpi_add_prt_dep() loop handling","id":"CVE-2026-93132"},"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 missing status check in the Linux kernel's RISC-V ACPI code can lead to a null pointer dereference, causing a system crash.","url":"https://insights.sbomify.com/CVE-2026-93133/"}