{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89767 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89767 is a high-severity vulnerability in Linux, published on 11 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-89767 and fix it if it is affected.\n\nWhat it is: CVE-2026-89767 is a high-severity vulnerability in Linux, published on 11 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-89767 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-89767/ (Markdown: https://insights.sbomify.com/CVE-2026-89767/index.md)","id":"CVE-2026-89767","markdown":"https://insights.sbomify.com/CVE-2026-89767/index.md","name":"CVE-2026-89767","record":{"aliases":["BELL-CVE-2026-89767","DEBIAN-CVE-2026-89767","GHSA-mvh9-78p9-62x7","UBUNTU-CVE-2026-89767"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel overlayfs","requires_auth":"low_privilege","summary":"An unprivileged user can cause a double unlock and double free in overlayfs, leading to a denial of service by wedging file creation operations.","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\novl: fix double end_creating() on the casefold-mismatch path\n\novl_create_real() releases the new dentry twice when the casefold\nconsistency check fails.  The S_IFDIR branch calls end_creating() and\nsets err, then falls through to the common out: label which calls\nend_creating() on the same dentry again:\n\n\tcase S_IFDIR:\n\t\tnewdentry = ovl_do_mkdir(ofs, dir, newdentry, attr-\u003emode);\n\t\terr = PTR_ERR_OR_ZERO(newdentry);\n\t\tif (!err \u0026\u0026 ofs-\u003ecasefold != ovl_dentry_casefolded(newdentry)) {\n\t\t\tpr_warn_ratelimited(...);\n\t\t\tend_creating(newdentry);\t/* first */\n\t\t\terr = -EINVAL;\n\t\t}\n\t\tbreak;\n\t...\n\tif (err)\n\t\tgoto out;\n\t...\n out:\n\tif (err) {\n\t\tend_creating(newdentry);\t/* second, same dentry */\n\t\treturn ERR_PTR(err);\n\t}\n\nend_creating() is end_dirop(), which does inode_unlock() on the parent\nand dput() on the dentry, so the parent directory's i_rwsem is unlocked\ntwice and the dentry is put twice.  The second unlock releases a lock\nthat is not held, which is what wedges every later creation under that\nparent, and the second dput() drops a reference that was never taken.\n\nThe branch was added by commit dfc7da402ccc (\"ovl: Check for casefold\nconsistency when creating new dentries\") as a bare dput(), which already\nreleased the reference twice; commit fe497f0759e0 (\"VFS: change\nvfs_mkdir() to unlock on failure.\") converted both sites to\nend_creating(), adding the double unlock.\n\nThis is reachable by an unprivileged user.  The casefold consistency of\nthe layers is validated at mount time in ovl_parse_layer(), and again on\nevery lookup in ovl_lookup_single(), but ofs-\u003eworkdir is the internal\n\"work\" subdirectory created inside the user-supplied workdir, and that\nsubdirectory is not re-checked.  Marking it casefolded after the mount\ntherefore makes every ovl_create_temp() inherit the wrong state - and\nthat path reaches ovl_create_real() through ovl_start_creating_temp(),\nwhich uses start_creating() with a generated name and so never runs the\nlookup-time check.\n\n  unshare -Urm\n  mount -t tmpfs -o casefold=utf8-12.1.0 tmpfs mnt\n  mkdir -p mnt/lower/d mnt/upper mnt/work mnt/merged\n  mount -t overlay ovl -o lowerdir=mnt/lower,\\\n        upperdir=mnt/upper,workdir=mnt/work mnt/merged\n  chattr +F mnt/work/work\n  mkdir mnt/merged/d/sub\t\t# directory copy-up\n\n  overlayfs: wrong inherited casefold (work/#5)\n\nand the next copy-up blocks forever on the parent's i_rwsem:\n\n  mkdir           D  start_creating+0x65/0xb0\n                     ovl_start_creating_temp+0xb0/0xe0 [overlay]\n                     ovl_create_temp+0xa3/0x1d0 [overlay]\n                     ovl_copy_up_one+0x1f1c/0x21c0 [overlay]\n                     ovl_copy_up_flags+0xf5/0x140 [overlay]\n                     ovl_create_object+0xb7/0x220 [overlay]\n                     ovl_mkdir+0x23/0x40 [overlay]\n\nDrop the end_creating() from the branch and let out: own the cleanup,\nwhich is what every other error path in this function already does.","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":"ovl: fix double end_creating() on the casefold-mismatch path","id":"CVE-2026-89767","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"fs: fix user path of nested backing files","id":"CVE-2026-89768"},"packages":[],"prev":{"headline":"pidfd: hold exec_update_lock around namespace ioctl","id":"CVE-2026-89766"},"products":["Linux"],"published":"2026-09-11","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-19","vendors":["Linux"]},"summary":"An unprivileged user can cause a double unlock and double free in overlayfs, leading to a denial of service by wedging file creation operations.","url":"https://insights.sbomify.com/CVE-2026-89767/"}