{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72190 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72190 is a 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-72190 and fix it if it is affected.\n\nWhat it is: CVE-2026-72190 is a 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-72190 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-72190/ (Markdown: https://insights.sbomify.com/CVE-2026-72190/index.md)","id":"CVE-2026-72190","markdown":"https://insights.sbomify.com/CVE-2026-72190/index.md","name":"CVE-2026-72190","record":{"aliases":["DEBIAN-CVE-2026-72190","GHSA-7xmj-mqhm-5492","UBUNTU-CVE-2026-72190"],"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 race condition in the Linux kernel NTFS driver can cause a deadlock during file rename operations, leading to a denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"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\nntfs: fix mrec_lock ABBA deadlock in rename\n\nntfs_file_fsync(), ntfs_dir_fsync() and __ntfs_write_inode() lock an\ninode's mrec_lock before taking the mrec_lock of its parent directory.\n\nntfs_rename() takes old_ni-\u003emrec_lock and old_dir_ni-\u003emrec_lock\nbefore taking new_ni-\u003emrec_lock for an existing target, or\nnew_dir_ni-\u003emrec_lock for a cross-directory rename.\nThis can deadlock when ntfs_file_fsync() or __ntfs_write_inode() holds\nthe target inode, or when ntfs_dir_fsync() holds a child target\ndirectory, while rename() holds the parent directory and waits for the\ntarget.\n\nFix this by locking the existing target inode before taking any parent\ndirectory mrec_lock. For cross-directory renames where the target parent\nis a descendant of the source parent, lock the target parent before the\nsource parent so the directory order matches the child-to-parent order used\nby ntfs_file_fsync(), ntfs_dir_fsync(), and __ntfs_write_inode().","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":"ntfs: fix mrec_lock ABBA deadlock in rename","id":"CVE-2026-72190","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":"ntfs3: validate split-point offset in indx_insert_into_buffer","id":"CVE-2026-72191"},"packages":[],"prev":{"headline":"ntfs: fail attrlist updates when the superblock is inactive","id":"CVE-2026-72189"},"products":["Linux"],"published":"2026-08-15","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-08-17","vendors":["Linux"]},"summary":"A race condition in the Linux kernel NTFS driver can cause a deadlock during file rename operations, leading to a denial of service.","url":"https://insights.sbomify.com/CVE-2026-72190/"}