CVE-2026-93252: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-358c-95r2-55gw
Share
Published
Advisory Summary

CVE-2026-93252 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-93252 at a Glance

CVE Identifier CVE-2026-93252
GHSA Identifier GHSA-358c-95r2-55gw
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-93252

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-93252, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix circular locking dependency in ocfs2_init_acl() A lockdep warning indicates a circular locking dependency between `&oi->ip_xattr_sem` and `&journal->j_trans_barrier`: WARNING: possible circular locking dependency detected is trying to acquire lock: (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_init_acl+0x2fd/0x7e0 fs/ocfs2/acl.c:367 but task is already holding lock: (&journal->j_trans_barrier){.+.+}-{4:4}, at: ocfs2_start_trans+0x3ab/0x700 fs/ocfs2/journal.c:369 The deadlock involves two code paths: Path 1 (setxattr) where `ocfs2_xattr_set()` acquires `ip_xattr_sem` (write) and then starts a transaction, which acquires `j_trans_barrier` (read); and Path 2 (mkdir/mknod) where `ocfs2_mknod()` starts a transaction (`j_trans_barrier` read) and then calls `ocfs2_init_acl()`, which attempts to acquire `ip_xattr_sem` (read) on the parent directory to retrieve the default ACL. Because rw_semaphores are subject to writer priority, a pending writer on `j_trans_barrier` (e.g., the journal commit thread) can cause Path 1 to block, while Path 2 is blocked waiting for Path 1 to release `ip_xattr_sem`. The patch fixes the lock ordering by precomputing the ACL state before starting the OCFS2 transaction, while preserving POSIX ACL storage semantics and the existing inode/security initialization order. By reading the parent directory's default ACL and preparing the new inode's ACLs outside the transaction, `ip_xattr_sem` is always acquired before `j_trans_barrier`. `struct ocfs2_acl_state` encapsulates the prepared ACL state, while `ocfs2_acl_init_prepare()` and `ocfs2_acl_init_release()` avoid code duplication between `ocfs2_mknod()` and `ocfs2_init_security_and_acl()`. `ocfs2_calc_xattr_init()` and `ocfs2_init_acl()` use this precomputed state, removing internal `ip_xattr_sem` acquisition and redundant disk reads. Additionally, remove the `ip_xattr_sem` acquisition from `ocfs2_xattr_set_handle()`. This function is only used while initializing a new inode that has not yet been inserted into the inode hash or attached to a dentry, meaning there is no risk of concurrent access and the lock is unnecessary.

References

NVD — CVE-2026-93252 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93252
git.kernel.org/stable/c/1222f7a318... WEB
https://git.kernel.org/stable/c/1222f7a3183b35c0c566899fdaead5c7c4043076
git.kernel.org/stable/c/4936d4464d... WEB
https://git.kernel.org/stable/c/4936d4464d1ae10b5fbba64374085a0dcc060560
git.kernel.org/stable/c/5b7b3c50c3... WEB
https://git.kernel.org/stable/c/5b7b3c50c39ad0dc27e7418981e01c4183273f89
git.kernel.org/stable/c/8931403ee3... WEB
https://git.kernel.org/stable/c/8931403ee3dcfe8a24a5267efec9d9460ab7a1b5
git.kernel.org/stable/c/8d88f52fbb... WEB
https://git.kernel.org/stable/c/8d88f52fbbbcc18adf4091a955511d0cf605bf11
git.kernel.org/stable/c/bd7c05fb4a... WEB
https://git.kernel.org/stable/c/bd7c05fb4a4776dff5a87b19008d28458647d15d
git.kernel.org/stable/c/caf3056936... WEB
https://git.kernel.org/stable/c/caf3056936fb8b5ce92e419cf8b246ce9c437343
git.kernel.org/stable/c/f8747d81aa... WEB
https://git.kernel.org/stable/c/f8747d81aa6d3efe3ee339a9d912ff3ca6e4d758

Frequently Asked Questions

What is CVE-2026-93252?
CVE-2026-93252 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-93252?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-93252?
CVE-2026-93252 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93252?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-358c-95r2-55gw",
  "modified" : "2026-09-24T18:31:24Z",
  "published" : "2026-09-24T18:31:24Z",
  "aliases" : [ "CVE-2026-93252" ],
  "details" : "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`&oi->ip_xattr_sem` and `&journal->j_trans_barrier`:\n\nWARNING: possible circular locking dependency detected\nis trying to acquire lock:\n (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_init_acl+0x2fd/0x7e0\n fs/ocfs2/acl.c:367\n\nbut task is already holding lock:\n (&journal->j_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.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93252"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1222f7a3183b35c0c566899fdaead5c7c4043076"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4936d4464d1ae10b5fbba64374085a0dcc060560"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5b7b3c50c39ad0dc27e7418981e01c4183273f89"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8931403ee3dcfe8a24a5267efec9d9460ab7a1b5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8d88f52fbbbcc18adf4091a955511d0cf605bf11"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bd7c05fb4a4776dff5a87b19008d28458647d15d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/caf3056936fb8b5ce92e419cf8b246ce9c437343"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f8747d81aa6d3efe3ee339a9d912ff3ca6e4d758"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-24T16:17:21Z"
  }
}