CVE-2026-92503: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-4ppx-vw73-jjc6
Share
Published
Advisory Summary

CVE-2026-92503 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-92503 at a Glance

CVE Identifier CVE-2026-92503
GHSA Identifier GHSA-4ppx-vw73-jjc6
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-92503

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-92503, 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: ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() Syzbot/stress-ng reported an ABBA deadlock in ext4 when exercising concurrent xattr workloads (using the ea_inode mount/format option). The deadlock occurs between the running transaction and the eviction thread: - Task 1 (stress-ng): Holds a reference to a shared mbcache_entry (ce) and calls ext4_xattr_inode_cache_find() -> ext4_iget() to retrieve the corresponding EA inode. Since the EA inode is currently being evicted, ext4_iget() blocks in __wait_on_freeing_inode() waiting for eviction to complete. - Task 2 (eviction thread): Currently evicting the same EA inode in ext4_evict_ea_inode(). It calls mb_cache_entry_wait_unused(oe) which blocks waiting for Task 1 to release the reference to the mbcache_entry. To break this deadlock, implement a new ext4_iget() configuration flag named EXT4_IGET_NOWAIT. When set, perform a non-blocking lookup of the inode via VFS's find_inode_nowait() API. If the inode is currently being evicted (marked with I_FREEING or I_WILL_FREE) or created (I_CREATING), or if it is not present in the VFS inode cache (cache miss), simply skip it (returning -ENOENT) rather than waiting for eviction/creation to complete, breaking the ABBA cycle. Since we return -ENOENT immediately on a cache miss, we never attempt to allocate a new inode or call iget_locked(), completely eliminating any TOCTOU race window. If the returned inode is I_NEW, wait for its initialization to clear via wait_on_new_inode(). If initialization fails and the inode is unhashed during wait_on_new_inode() waking up (e.g., due to an I/O read error in another thread), safely drop the reference and return -ENOENT. This unhashed check is executed unconditionally on all cache-hit pathways to properly handle concurrent initialization failures. Finally, standard validation checks (including is_bad_inode, EXT4_EA_INODE_FL, file_acl, and xattr flags) are executed as normal inside check_igot_inode() to fully guarantee VFS-layer safety. In ext4_xattr_inode_cache_find(), invoke ext4_iget() with the new EXT4_IGET_NOWAIT flag to perform the non-blocking cache search.

References

NVD — CVE-2026-92503 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-92503
git.kernel.org/stable/c/03438084a7... WEB
https://git.kernel.org/stable/c/03438084a7b8621fb5c762dd3d04cff5f2630fb2
git.kernel.org/stable/c/074d062040... WEB
https://git.kernel.org/stable/c/074d0620401974cbfa9b63684cdfae99c7b2059c
git.kernel.org/stable/c/7720fddd1f... WEB
https://git.kernel.org/stable/c/7720fddd1fe344d14be258a2028f74ebf1569511

Frequently Asked Questions

What is CVE-2026-92503?
CVE-2026-92503 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-92503?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-92503?
CVE-2026-92503 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-92503?
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-4ppx-vw73-jjc6",
  "modified" : "2026-10-15T12:30:51Z",
  "published" : "2026-09-17T18:32:06Z",
  "aliases" : [ "CVE-2026-92503" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\next4: fix ABBA deadlock in ext4_xattr_inode_cache_find()\n\nSyzbot/stress-ng reported an ABBA deadlock in ext4 when exercising\nconcurrent xattr workloads (using the ea_inode mount/format option).\n\nThe deadlock occurs between the running transaction and the eviction\nthread:\n- Task 1 (stress-ng): Holds a reference to a shared mbcache_entry (ce)\n  and calls ext4_xattr_inode_cache_find() -> ext4_iget() to retrieve\n  the corresponding EA inode. Since the EA inode is currently being\n  evicted, ext4_iget() blocks in __wait_on_freeing_inode() waiting for\n  eviction to complete.\n- Task 2 (eviction thread): Currently evicting the same EA inode in\n  ext4_evict_ea_inode(). It calls mb_cache_entry_wait_unused(oe) which\n  blocks waiting for Task 1 to release the reference to the mbcache_entry.\n\nTo break this deadlock, implement a new ext4_iget() configuration flag\nnamed EXT4_IGET_NOWAIT. When set, perform a non-blocking lookup of the\ninode via VFS's find_inode_nowait() API.\n\nIf the inode is currently being evicted (marked with I_FREEING or\nI_WILL_FREE) or created (I_CREATING), or if it is not present in the VFS\ninode cache (cache miss), simply skip it (returning -ENOENT) rather than\nwaiting for eviction/creation to complete, breaking the ABBA cycle.\n\nSince we return -ENOENT immediately on a cache miss, we never attempt to\nallocate a new inode or call iget_locked(), completely eliminating any\nTOCTOU race window.\n\nIf the returned inode is I_NEW, wait for its initialization to clear via\nwait_on_new_inode(). If initialization fails and the inode is unhashed\nduring wait_on_new_inode() waking up (e.g., due to an I/O read error in\nanother thread), safely drop the reference and return -ENOENT. This\nunhashed check is executed unconditionally on all cache-hit pathways to\nproperly handle concurrent initialization failures.\n\nFinally, standard validation checks (including is_bad_inode,\nEXT4_EA_INODE_FL, file_acl, and xattr flags) are executed as normal inside\ncheck_igot_inode() to fully guarantee VFS-layer safety.\n\nIn ext4_xattr_inode_cache_find(), invoke ext4_iget() with the new\nEXT4_IGET_NOWAIT flag to perform the non-blocking cache search.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-92503"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/03438084a7b8621fb5c762dd3d04cff5f2630fb2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/074d0620401974cbfa9b63684cdfae99c7b2059c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7720fddd1fe344d14be258a2028f74ebf1569511"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:52Z"
  }
}