CVE-2026-53125: Software Security Vulnerability Vulnerability
MODERATECVE-2026-53125 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (CWE-667: Improper Locking) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.. Remediation is available in the latest vendor maintenance releases.
CVE-2026-53125 at a Glance
Security Impact
CVSS: 5.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
How to Fix CVE-2026-53125
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.
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:treeHow to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-53125, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:treeAnalyze 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 CWE-667: Improper Locking, where the product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. 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
References
Frequently Asked Questions
What is CVE-2026-53125?
Which Software versions are affected?
What version fixes CVE-2026-53125?
What is the CVSS score of CVE-2026-53125?
What CWE is associated with CVE-2026-53125?
How can I check Maven dependencies for CVE-2026-53125?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9m96-3qwq-4728",
"modified" : "2026-07-23T21:30:35Z",
"published" : "2026-06-24T18:32:48Z",
"aliases" : [ "CVE-2026-53125" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmd: fix array_state=clear sysfs deadlock\n\nWhen \"clear\" is written to array_state, md_attr_store() breaks sysfs\nactive protection so the array can delete itself from its own sysfs\nstore method.\n\nHowever, md_attr_store() currently drops the mddev reference before\ncalling sysfs_unbreak_active_protection(). Once do_md_stop(..., 0)\nhas made the mddev eligible for delayed deletion, the temporary\nkobject reference taken by sysfs_break_active_protection() can become\nthe last kobject reference protecting the md kobject.\n\nThat allows sysfs_unbreak_active_protection() to drop the last\nkobject reference from the current sysfs writer context. kobject\nteardown then recurses into kernfs removal while the current sysfs\nnode is still being unwound, and lockdep reports recursive locking on\nkn->active with kernfs_drain() in the call chain.\n\nReproducer on an existing level:\n1. Create an md0 linear array and activate it:\n mknod /dev/md0 b 9 0\n echo none > /sys/block/md0/md/metadata_version\n echo linear > /sys/block/md0/md/level\n echo 1 > /sys/block/md0/md/raid_disks\n echo \"$(cat /sys/class/block/sdb/dev)\" > /sys/block/md0/md/new_dev\n echo \"$(($(cat /sys/class/block/sdb/size) / 2))\" > \\\n\t/sys/block/md0/md/dev-sdb/size\n echo 0 > /sys/block/md0/md/dev-sdb/slot\n echo active > /sys/block/md0/md/array_state\n2. Wait briefly for the array to settle, then clear it:\n sleep 2\n echo clear > /sys/block/md0/md/array_state\n\nThe warning looks like:\n\n WARNING: possible recursive locking detected\n bash/588 is trying to acquire lock:\n (kn->active#65) at __kernfs_remove+0x157/0x1d0\n but task is already holding lock:\n (kn->active#65) at sysfs_unbreak_active_protection+0x1f/0x40\n ...\n Call Trace:\n kernfs_drain\n __kernfs_remove\n kernfs_remove_by_name_ns\n sysfs_remove_group\n sysfs_remove_groups\n __kobject_del\n kobject_put\n md_attr_store\n kernfs_fop_write_iter\n vfs_write\n ksys_write\n\nRestore active protection before mddev_put() so the extra sysfs\nkobject reference is dropped while the mddev is still held alive. The\nactual md kobject deletion is then deferred until after the sysfs\nwrite path has fully returned.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
} ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-53125"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/2aa72276fab9851dbd59c2daeb4b590c5a113908"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/62c44566da7493ee48ef17e8507bb798338a07cb"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/92ad0ec509ffb188d8f849b63148664df37b4a52"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-667" ],
"severity" : "MODERATE",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-06-24T17:17:27Z"
}
}