{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93252 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93252 is a 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-93252 and fix it if it is affected.\n\nWhat it is: CVE-2026-93252 is a 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-93252 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-93252/ (Markdown: https://insights.sbomify.com/CVE-2026-93252/index.md)","id":"CVE-2026-93252","markdown":"https://insights.sbomify.com/CVE-2026-93252/index.md","name":"CVE-2026-93252","record":{"aliases":["BELL-CVE-2026-93252","DEBIAN-CVE-2026-93252","GHSA-358c-95r2-55gw","UBUNTU-CVE-2026-93252"],"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 local attacker can trigger a deadlock in the OCFS2 filesystem via circular locking, causing 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\nocfs2: fix circular locking dependency in ocfs2_init_acl()\n\nA lockdep warning indicates a circular locking dependency between\n`\u0026oi-\u003eip_xattr_sem` and `\u0026journal-\u003ej_trans_barrier`:\n\nWARNING: possible circular locking dependency detected\nis trying to acquire lock:\n (\u0026oi-\u003eip_xattr_sem){++++}-{4:4}, at: ocfs2_init_acl+0x2fd/0x7e0\n fs/ocfs2/acl.c:367\n\nbut task is already holding lock:\n (\u0026journal-\u003ej_trans_barrier){.+.+}-{4:4}, at: ocfs2_start_trans+0x3ab/0x700\n fs/ocfs2/journal.c:369\n\nThe deadlock involves two code paths: Path 1 (setxattr) where\n`ocfs2_xattr_set()` acquires `ip_xattr_sem` (write) and then starts a\ntransaction, which acquires `j_trans_barrier` (read); and Path 2\n(mkdir/mknod) where `ocfs2_mknod()` starts a transaction (`j_trans_barrier`\nread) and then calls `ocfs2_init_acl()`, which attempts to acquire\n`ip_xattr_sem` (read) on the parent directory to retrieve the default ACL.\n\nBecause rw_semaphores are subject to writer priority, a pending writer on\n`j_trans_barrier` (e.g., the journal commit thread) can cause Path 1 to\nblock, while Path 2 is blocked waiting for Path 1 to release\n`ip_xattr_sem`.\n\nThe patch fixes the lock ordering by precomputing the ACL state before\nstarting the OCFS2 transaction, while preserving POSIX ACL storage\nsemantics and the existing inode/security initialization order. By reading\nthe parent directory's default ACL and preparing the new inode's ACLs\noutside the transaction, `ip_xattr_sem` is always acquired before\n`j_trans_barrier`.\n\n`struct ocfs2_acl_state` encapsulates the prepared ACL state, while\n`ocfs2_acl_init_prepare()` and `ocfs2_acl_init_release()` avoid code\nduplication between `ocfs2_mknod()` and `ocfs2_init_security_and_acl()`.\n`ocfs2_calc_xattr_init()` and `ocfs2_init_acl()` use this precomputed\nstate, removing internal `ip_xattr_sem` acquisition and redundant disk\nreads.\n\nAdditionally, remove the `ip_xattr_sem` acquisition from\n`ocfs2_xattr_set_handle()`. This function is only used while initializing a\nnew inode that has not yet been inserted into the inode hash or attached to\na dentry, meaning there is no risk of concurrent access and the lock is\nunnecessary.","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":"ocfs2: fix circular locking dependency in ocfs2_init_acl()","id":"CVE-2026-93252","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"sched/isolation: Defer freeing of cpumask memblock memory to initcall","id":"CVE-2026-93253"},"packages":[],"prev":{"headline":"ACPI: bus: Introduce acpi_bus_get_primary_device()","id":"CVE-2026-93251"},"products":["Linux"],"published":"2026-09-24","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-10-19","vendors":["Linux"]},"summary":"A local attacker can trigger a deadlock in the OCFS2 filesystem via circular locking, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2026-93252/"}