{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72368 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72368 is a high-severity vulnerability in Linux, published on 15 Aug 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-72368 and fix it if it is affected.\n\nWhat it is: CVE-2026-72368 is a high-severity vulnerability in Linux, published on 15 Aug 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-72368 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-72368/ (Markdown: https://insights.sbomify.com/CVE-2026-72368/index.md)","id":"CVE-2026-72368","markdown":"https://insights.sbomify.com/CVE-2026-72368/index.md","name":"CVE-2026-72368","record":{"aliases":["DEBIAN-CVE-2026-72368","GHSA-h4x8-g6jq-m2w5","UBUNTU-CVE-2026-72368"],"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 double unlock in the Linux kernel cachefiles module can corrupt lock state, potentially leading to system instability or denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"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\ncachefiles: Fix double unlock in nomem_d_alloc error path\n\nWhen start_creating() fails and returns -ENOMEM, it has already\nreleased the parent directory lock in __start_dirop():\n\n    static struct dentry *__start_dirop(...)\n    {\n        ...\n        inode_lock_nested(dir, I_MUTEX_PARENT);\n        dentry = lookup_one_qstr_excl(name, parent, lookup_flags);\n        if (IS_ERR(dentry))\n            inode_unlock(dir);  \u003c-- Lock released on error\n        return dentry;\n    }\n\nHowever, the nomem_d_alloc error path in cachefiles_get_directory()\nunconditionally calls inode_unlock(d_inode(dir)) again, causing a\ndouble unlock that corrupts the rwsem state.\n\nThis is a leftover from commit 7ab96df840e60 which replaced manual\nlocking with start_creating() but failed to update the nomem_d_alloc\npath (while correctly updating mkdir_error and lookup_error paths).","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 unlock in nomem_d_alloc error path","id":"CVE-2026-72368","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"minix: avoid overflow in bitmap block count calculation","id":"CVE-2026-72369"},"packages":[],"prev":{"headline":"iomap: guard io_size EOF trim against concurrent truncate underflow","id":"CVE-2026-72367"},"products":["Linux"],"published":"2026-08-15","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-08-17","vendors":["Linux"]},"summary":"A double unlock in the Linux kernel cachefiles module can corrupt lock state, potentially leading to system instability or denial of service.","url":"https://insights.sbomify.com/CVE-2026-72368/"}