{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97594 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97594 is a high-severity use after free 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-97594 and fix it if it is affected.\n\nWhat it is: CVE-2026-97594 is a high-severity use after free 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-97594 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-97594/ (Markdown: https://insights.sbomify.com/CVE-2026-97594/index.md)","id":"CVE-2026-97594","markdown":"https://insights.sbomify.com/CVE-2026-97594/index.md","name":"CVE-2026-97594","record":{"aliases":["AZL-104747","BELL-CVE-2026-97594","DEBIAN-CVE-2026-97594","GHSA-236x-phcf-6qmf","UBUNTU-CVE-2026-97594"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A use-after-free in the Linux kernel Landlock subsystem allows local attackers to trigger memory corruption via race conditions, potentially leading to privilege escalation.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/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\nlandlock: Fix use-after-free of the source's parent directory\n\ncurrent_check_refer_path() reads old_dentry-\u003ed_parent without holding a\nreference nor a lock on it, and then dereferences it in\ncollect_domain_accesses() and in the audit record.\n\nA reference on a child does not pin its parent: __d_move() reassigns\ndentry-\u003ed_parent and drops the reference the child held on its former\nparent.  hook_path_rename() is not affected because the rename path\ncalls lock_rename() before the hook, so the source cannot be reparented\nunder it.  hook_path_link() has no such protection: filename_linkat()\nholds a reference on the source dentry but neither locks nor references\nits parent, so a concurrent rename(2) can reparent the source while\nsecurity_path_link() runs, and the former parent can then be removed and\nfreed while the hook walks it.\n\nA process can trigger this after entering a Landlock domain that handles\nat least one filesystem access right.  The process can then race a\nlinkat(2) loop against rename(2) and rmdir(2):\n\n  BUG: KASAN: slab-use-after-free in collect_domain_accesses+0x278/0x290\n  Read of size 4 at addr ffff888160bd53f4 by task llrepro2/549\n   collect_domain_accesses+0x278/0x290\n   current_check_refer_path+0x952/0x1120\n   security_path_link+0x1be/0x320\n   filename_linkat+0x342/0x6d0\n   __x64_sys_linkat+0xfa/0x150\n  Freed by task 562:\n   kmem_cache_free+0x139/0x4c0\n   i_callback+0x4b/0x80\n   rcu_core+0x7dc/0x10a0\n\nTake a reference on the dentry selected as the source parent, using\ndget() for the common-mount-root case and dget_parent() otherwise.\nRelease it after the hierarchy walk and synchronous audit logging.\n\n[mic: Clarify the caller, reachability, and reference handling]","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":"landlock: Fix use-after-free of the source's parent directory","id":"CVE-2026-97594","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":"mac802154: fix use-after-free of sdata via queued RX frames","id":"CVE-2026-97595"},"packages":[],"prev":{"headline":"iommu/s390: Fix NULL dereference in iova_to_phys() with ZPCI_TABLE_TYPE_RFX","id":"CVE-2026-97593"},"products":["Linux"],"published":"2026-09-25","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-21","vendors":["Linux"]},"summary":"A use-after-free in the Linux kernel Landlock subsystem allows local attackers to trigger memory corruption via race conditions, potentially leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-97594/"}