{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93810 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93810 is a high-severity use after free vulnerability in Linux, published on 24 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-93810 and fix it if it is affected.\n\nWhat it is: CVE-2026-93810 is a high-severity use after free vulnerability in Linux, published on 24 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-93810 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-93810/ (Markdown: https://insights.sbomify.com/CVE-2026-93810/index.md)","id":"CVE-2026-93810","markdown":"https://insights.sbomify.com/CVE-2026-93810/index.md","name":"CVE-2026-93810","record":{"aliases":["AZL-103703","BELL-CVE-2026-93810","DEBIAN-CVE-2026-93810","GHSA-6jcf-xjrv-rxjr","UBUNTU-CVE-2026-93810"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A double fput() error in the Linux kernel's cachefiles module can lead to use-after-free conditions, potentially causing crashes or code execution.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncachefiles: Fix double fput\n\nFix a double fput() in error handling in cachefiles_create_tmpfile().","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":"cachefiles: Fix double fput","id":"CVE-2026-93810","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"ksmbd: Fix acl.sd_buf memory leak and invalid sd_size error handling","id":"CVE-2026-93811"},"packages":[],"prev":{"headline":"drm/amdgpu: flush pending RCU callbacks on module unload","id":"CVE-2026-93809"},"products":["Linux"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-03","vendors":["Linux"]},"summary":"A double fput() error in the Linux kernel's cachefiles module can lead to use-after-free conditions, potentially causing crashes or code execution.","url":"https://insights.sbomify.com/CVE-2026-93810/"}