{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93106 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93106 is an use after free 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-93106 and fix it if it is affected.\n\nWhat it is: CVE-2026-93106 is an use after free 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-93106 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-93106/ (Markdown: https://insights.sbomify.com/CVE-2026-93106/index.md)","id":"CVE-2026-93106","markdown":"https://insights.sbomify.com/CVE-2026-93106/index.md","name":"CVE-2026-93106","record":{"aliases":["BELL-CVE-2026-93106","DEBIAN-CVE-2026-93106","GHSA-ggxj-6q52-m3ww","UBUNTU-CVE-2026-93106"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A use-after-free vulnerability in the Linux kernel's crash_dump module allows local attackers with high privileges to cause a system crash or potentially escalate privileges.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\ncrash_dump: release keyring reference at the correct time\n\nrestore_dm_crypt_keys_to_thread_keyring() gets a reference to the user\nkeyring before restoring the saved dm-crypt keys.\n\nThe same keyring reference is then passed to add_key_to_keyring() for each\nsaved key, but add_key_to_keyring() drops that reference on every call.\nThis is only balanced when exactly one key is restored. With multiple\nkeys, the keyring reference is dropped too many times and may trigger a\nrefcount underflow or use-after-free.\n\nWhen more than five keys are restored, a refcount underflow/use-after-free\nwarning can be triggered.\n\nThe early error paths after lookup_user_key() also return without dropping\nthe keyring reference.\n\nKeep ownership of the keyring reference in\nrestore_dm_crypt_keys_to_thread_keyring(), drop it once on all exit paths,\nand make add_key_to_keyring() only use the reference without consuming it.","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":"crash_dump: release keyring reference at the correct time","id":"CVE-2026-93106","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state","id":"CVE-2026-93107"},"packages":[],"prev":{"headline":"esp: do not unref managed frag pages in esp_ssg_unref()","id":"CVE-2026-93105"},"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 use-after-free vulnerability in the Linux kernel's crash_dump module allows local attackers with high privileges to cause a system crash or potentially escalate privileges.","url":"https://insights.sbomify.com/CVE-2026-93106/"}